Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Installating Datameer X on MapR

The Datameer X software is available for installation from your my.datameer archive repository located at my.datameer.com. You must have the MapR repository configured properly in order to install Datameer. See MapR documentation for instructions.

Datameer X is currently available for distribution for Mac, Redhat, Suse, Unbuntu, or Windows named mapr-zip.

Note
titleDependencies

Datameer X requires that mapr-core is available on the host machine and that a fully configured MapR cluster is connected to the host machine. These packages must be installed and the MapR services configured prior to installing mapr-zip.

...

Pre-installation

The Datameer X package built for MapR Hadoop distributions doesn't include native libs, so you need copy the libs from the cluster to Datameer X using the following command:

...

Once the package has been installed successfully, the Datameer X service automatically starts and is ready for use on port 8080 of the host machine. Make sure to use a Flash-enabled and /wiki/spaces/DASSB100/pages/32569526864 when accessing this URL.

The Datameer X software is installed on the machine in /opt/datameer/datameer-3.1.1-mapr.

...

All Datameer-related files are stored in this directory including control scripts and logs. The bin directory contains all executable scripts, most notably conductor.sh which controls the Datameer X server. You can also find SQL scripts for database initialization and various other tools. All logging output is directed to files in the logs directory, the most interesting of which is conductor.log. This is where the most valuable logging information related to running the Datameer X system will be written.

Note
titleErrors During Installation

After installing the mapr-datameer package, if you see an error similar to:

ERROR Cidcache fs/client/fileclient/cc/cidcache.cc:1017 Thread: 1075886400 Lookup of volume mapr.cluster.root failed, error Connection reset by peer(104), CLDB: 172.16.148.131:7222 trying another CLDB

or in the Datameer X conductor.log

java.io.IOException: Could not create FileClient

then you have most likely installed Datameer X without first properly configuring a MapR cluster. Stop the Datameer X application with the following command:

Code Block
/etc/init.d/das-conductor stop

Configure and start the MapR components and then re-start the Datameer X application using the command:

Code Block
/etc/init.d/das-conductor start

Stopping and starting Datameer

Datameer X starts automatically upon successful installation. The mapr-datameer package also installs a script in /etc/init.d/das-conductor which can be used to control the Datameer X process.

In case Datameer X doesn't start automatically (only if you have experienced errors during installation), you can run the startup script located in /etc/init.d/das-conductor with the start option.

...

To stop a running instance of Datameer , X use the stop option by entering the following command:

...

After activating your trial license, navigate to the Login screen either by clicking Login Now on the trial activation screen or by visiting port 8080 on the machine where Datameer X is installed. You can now login with the default administrator account by entering the credentials below and clicking Login.

Username

Password

admin

admin

Anchor
zero_config
zero_config
Connecting Datameer X to a MapR Cluster with Zero Configuration HA for Resource Manager

MAPR Zero Configuration is automatically detected by Datameer X when the Hadoop Cluster is configured with MAPR grid mode. 

Info
titleAs of Datameer X v6.1

An additional label with a checkmark is displayed on the cluster settings page when Zero Configuration HA is enabled.

Image RemovedImage Added

Learn more about MapR's Zero Configuration Failover for the ResourceManager.

MapR Security

According to Enabling and Disabling Security Features and Getting started with MapR Security, MapR is runs cluster nodes and Java virtual machines (JVMs) with its own truststore.

...