MapR 4.0.x Documentation : Quick Installation Guide

This installation guide covers the Quick Install method, which is the recommended procedure for basic installations, such as proof of concept deployments. The MapR quick installer automates the process of configuring a Hadoop cluster and installing MapR software based on node type.

You can install the MapR distribution for Hadoop on a set of nodes from any machine that can connect to the nodes. Using the quick installer, you can configure each node in a MapR cluster as one of the following types: 

Node TypeDescription
Control Node

Control nodes manage the operation of the cluster. Control nodes host the ZooKeeper, CLDB, JobTracker, ResourceManager, and Webserver services. One control node also hosts the HistoryServer.

Data Nodes

Data nodes host the NodeManager, TaskTracker, and FileServer services. These nodes store data, run YARN applications and MapReduce jobs, and process table data.

Control-as-data Nodes

Control-as-data nodes combine control and data node functionality. This node type is appropriate for small clusters.

Client Nodes

Client nodes provide controlled user access to the cluster.

For more information about node types, see Understanding Node Types.

Ecosystem Component Installation

In addition to installing the core components of the MapR Hadoop distribution, the MapR quick installer supports installation of Apache Spark, Hive, and HBase. To install the Spark and Hive ecosystem components, you must use the quick installer configuration file. See Installing Spark and Installing Hive. You can also use the configuration file to install HBase, however when you run the quick installer in interactive mode, the installer prompts you to see if you want HBase or MapR-DB installed. Entering y at these prompts instructs the installer to install HBase and/or MapR-DB during the installation process. 

Installation Steps

To successfully install MapR using the quick installer, complete the following steps:

  1. Make sure your installation machine and nodes meet all of the prerequisites.
  2. Prepare for the installation and set up the installation machine.
  3. Run the quick installer.
  4. Complete the post installation steps.

For more information and guidelines about the MapR installation process, see About Installation.

You may also want to review the following sections in this guide:


Verify that your installation machine and the nodes that you plan to install MapR on meet the required prerequisites.

Installation Machine Prerequisites

The machine from which you run the quick installer must run one of the following operating systems:

Operating SystemVersion


12.04 or later
RedHat with the EPEL repository installed 6.1 or later
CentOS with the EPEL repository installed 6.1 or later


To install from a machine running SuSE, you must create a symbolic link named, that points to under /usr/lib64 before you install.

cd /usr/lib64
ln -s 

MapR Node Prerequisites

The nodes that you install MapR on must meet the following prerequisites:

Python2.6 or later
Java1.7 or 1.8


You can install MapR on the following 64-bit operating systems:

  • RedHat 6.1 or later
  • CentOS 6.1 or later
  • Ubuntu 12.04 or later
  • SUSE 11SP2

The operating system on each node must meet the listed package dependencies.
The quick installer should install these dependencies automatically. If not, you can install them manually.
For RedHat and CentOS, you must have the EPEL repository installed for the quick installer to install the dependencies automatically. 

Ubuntu/SUSE Package Dependencies
RedHat/CentOS Package Dependencies

Note: Install these packages manually if the quick installer cannot resolve them.

Refer to the Interoperability Matrix  for more information.

Installing the EPEL Repository

If you need to install the EPEL repository, complete the following steps: 

  1. Download the version of the EPEL repository that corresponds to the version of your operating system:

  2. Issue the following command to install the EPEL repository, replacing version with the EPEL version: 

    rpm -Uvh epel-release-<version>*.rpm
    rpm -Uvh epel-release-6*.rpm

Before You Run the Quick Installer

Before you run the quick installer to install MapR on your cluster, verify that you have completed all of the preparation tasks and set up the installation machine.

Preparing for Installation

Verify that you have completed the following preparation tasks before you set up the installation machine:

Determine the number
of control nodes 
The MapR installer supports one or three control nodes. Three control nodes are typically sufficient for
clusters up to approximately 100 nodes.
Determine the data
and client nodes 
The MapR installer supports an arbitrary number of data or client nodes.
Ensure all nodes
have internet access 
For online installation only.

Ensure access to a
local repository of MapR
packages and Linux
distribution repositories 

For offline installation only. Ensure that you have access to a local repository of MapR packages and to Linux
distribution repositories. For information about how to create a local repository, see Using a Local Repository
Decide if you will install
Spark or Hive 

If you decide to install Apache ecosystem projects, like Spark or Hive, you must install using the configuration file.

Verify that all nodes you
plan to install on are
configured to have the
same login information

If you are using the quick installer in interactive mode, described later in this document, verify that all the nodes
have the same disks for use by the MapR Hadoop Platform.
Identify disks to allocate
to the MapR file sytem  

For each node in the cluster, you must identify which disks you want to allocate to the MapR file system.
If the same set of disks and partitions applies to all nodes in the cluster, you can use 
interactive mode for the installer. 
To specify a distinct set of disks and partitions for individual cluster nodes, you need to use the configuration file.
The installer’s interactive mode and configuration files are discussed in depth later in this document.

Use the lsblk or fdisk -l commands to determine the full path for the disks that you plan to use.

  • The lsblk command prints the available block devices. 
  • The fdisk -l command prints the disk names with their full paths. 

The following examples show sample outputs that print when you run the commands: 

[root@ip-<ip_address> ~]# lsblk 
xvdf 202:80   0 37.5G  0 disk 
xvdg 202:96   0 37.5G  0 disk 
xvde 202:64   0    8G  0 disk /
Disk /dev/sda: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sdb: 10.6 GB, 10632560640 bytes
255 heads, 63 sectors/track, 1292 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ab664

Device Boot         Start         End      Blocks   Id  System
/dev/sda1   *           1          64      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              64        1293     9870336   8e  Linux LVM 

Setting Up the Installation Machine

Complete the following steps to set up the installation machine:

  1. Download the mapr-setup file for the MapR version that you plan to install. The following examples use the wget utility to download mapr-setup for MapR version 4.0.2, however you can also download mapr-setup for MapR v4.0.1. 

  2. Navigate to the directory where you downloaded mapr-setup, and enable execute permissions with the following command: 

    chmod 755 mapr-setup
  3. Run mapr-setup to unpack the installer files to the /opt/mapr-installer directory. The user running mapr-setup must have write access to the /opt and /tmp directories. You can execute mapr-setup with sudo privileges:

    sudo ./mapr-setup

    The system extracts the installer and copies the set up files to /opt/mapr-install.  The system prompts you to run /opt/mapr-installer/bin/install to begin the installation process. Follow the guidelines in the Using the MapR Quick Installer section.

This installer enables password-authenticated ssh login, which remains enabled after installation. You can disable password authentication for ssh manually after installation by adding the following line to the sshd_config file and restarting ssh: PasswordAuthentication no

Using the MapR Quick Installer

Use the MapR quick installer in interactive mode from the command line or provide a configuration file. If you plan to use the configuration file, you can get details about the format and syntax of the file in the Quick Installer Configuration File section. For a full list of quick installer syntax and installation options, refer to the Quick Installer Options section.

Running the Quick Installer

To run the quick installer, login as the root user or use sudo, and issue the following command:

/opt/mapr-installer/bin/install new

As of 4.0.2, you do not need to pass login credentials through the command line when you run the installer. The quick installer prompts you for ssh or private key login credentials based on the information that you provide during configuration.

Interactive Mode Sample Session

The following output reflects a typical interactive-mode session with the MapR quick installer. User input is in bold.

=                                                                             =
=  __  __                ____    ___              _          _  _             =
= |  \/  |  __ _  _ __  |  _ \  |_ _| _ __   ___ | |_  __ _ | || |  ___  _ __ =
= | |\/| | / _` || '_ \ | |_) |  | | | '_ \ / __|| __|/ _` || || | / _ \| '__|=
= | |  | || (_| || |_) ||  _ <   | | | | | |\__ \| |_| (_| || || ||  __/| |   =
= |_|  |_| \__,_|| .__/ |_| \_\ |___||_| |_||___/ \__|\__,_||_||_| \___||_|   =

=                 |_|                                                         =
=                                                                             =



An Installer config file is typically used by experienced MapR admins to skip through the interview process.

Do you have a config file (y/n) [n]: n

Enter the hostnames of all the control nodes separated by spaces or commas []: control-host-01

Only 1 or 3 control nodes are supported.

Hostname resolution of all nodes in the cluster must be consistent across cluster nodes and the multi-node installer's driver node (the node from which the installation is launched). For example, either all nodes must be specified with a fully qualified domain name (FQDN) or none of the nodes can be specified with their FQDN.

Enter the hostnames of all the data nodes separated by spaces or commas []: data-host-01,data-host-02
Set MapR User Name [mapr]:
Set MapR User Password [mapr]:

Is this cluster going to run YARN? (y/n) [y]:

When you install MapR 4.0.2, the quick installer enables zero configuration for ResourceManager, which provides automatic failover. For more information about zero configuration, see Zero Configuration Failover for the ResourceManager.

Is this cluster going to run MapReduce1? (y/n) [n]:
Is this cluster going to run Apache HBase? (y/n) [n]:
Is this cluster going to run MapR-DB? (y/n) [y]:

Enter the full path of disks for hosts separated by spaces or commas []: /dev/xvdf,/dev/xvdg

The MapR quick installer uses the same set of disks and partitions for each node in the cluster. To specify disks and partitions individually for each node, use a configuration file.

Once you have specified the cluster’s configuration information, the MapR quick installer displays the configuration and asks for confirmation:

       Current Information (Please verify if correct)

       Accessibility settings:

           Cluster Name: ""
           MapR User Name: "mapr"
           MapR Group Name: "mapr"
           MapR User UID: "2000"
           MapR User GID: "2000"
           MapR User Password (Default: mapr): "****"

       Functional settings:

           WireLevel Security: "n"
           MapReduce Services: "n"
           YARN: "y" 

           MapR-DB: "y"
           HBase: "n"
           Disks to use: "/dev/xvdf,/dev/xvdg"
           Client Nodes: ""
           Control Nodes: "control-host-01"
           Data Nodes: "data-host-01,data-host-02"
           Repository (will download core software from here): ""
           Ecosystem Repository (will download packages like Pig, Hive etc from here): ""
           MapR Version to Install: "4.0.2"
           Java Version to Install: "OpenJDK7"
           Allow Control Nodes to function as Data Nodes (Not recommended for large clusters): "n"
           Local Repository: "n"

       Metrics settings:

           Metrics DB Host and Port: ""
           Metrics DB User Name: ""
           Metrics DB User Password: ""
           Metrics DB Schema: ""

(c)ontinue with install, (m)odify options, or save current configuration and (a)bort? (c/m/a) [c]: m

Before you proceed with the installation, you can modify various settings. For example, you can set the stripe width (the number of disks in each storage pool) by selecting the sw option from the modification menu. You should also force format your disks if they were previously used in a MapR installation.

For a complete list of configuration properties that you can change, see About Installation.

As you continue with the installation, the installer prompts you for the login credentials:

When prompted for a private key, you must enter y or n.

(c)ontinue with install, (m)odify options, or save current configuration and (a)bort? (c/m/a) [c]: c
SSH Username: root
Private Key? [y/n]: y
Path to Private Key: ~/keys/private_key.pem
SSH password: ****
Now running on Added Control Nodes: [control-host-01]

The quick installer first sets up the control nodes in parallel, then sets up data nodes in groups of ten nodes at a time. Pre-requisite packages are automatically downloaded and installed by the MapR quick installer.

Quick Installer Options

When you use options, include the new or the add parameter after the option to specify a new installation or an addition to an existing installation.

mapr-install [-h] [-s] [-U SUDO_USER] [-u REMOTE_USER]
                      [--private-key PRIVATE_KEY_FILE] [-k] [-K]
                      [--skip-checks] [--quiet] [--cfg CFG_LOCATION]
                      [--debug] [--password REMOTE_PASS]
                      [--sudo-password SUDO_PASS]
                      {new,add} ...

The following table lists the available options with their descriptions:




-h or --help

Displays help text.

-u or --user <remote user>

Specifies a user name that the MapR quick installer uses to connect to the cluster nodes.

-k or --ask-pass

Request the remote ssh password interactively.


Specifies the remote ssh user’s password. Note: You cannot use this option if you are specifying a private key with the --private-key option.

--private-key <path to private key file>

Specifies a path to a private key file used to authenticate the connection. Note: You cannot use the --password option if you are specifying a private key.

-s or --sudo

Executes operations on the target nodes using sudo. If the user specified with the -u option is not root, you must use this option.

-U or --sudo-user <sudo user>

Specifies the username of the sudo user. This username is root on most systems.

-K or --ask-sudo-pass

Requests the sudo password interactively.


Specifies the sudo user’s password.


Skips requirement pre-checks.


Runs the installer in a non-interactive mode.

--cfg <path to config file location>

Installs with the configuration file at the specified path.


Run in debug mode. Debug mode includes more verbose reports on installer activity.

Quick Installer Manifest File

The MapR quick installer generates a manifest file in the /opt/mapr-installer/var directory named manifest.yml. The manifest file stores your cluster’s installation state. When you add and option to an existing installation, the quick installer checks the manifest for the cluster’s current installation state.

Since the manifest file is generated on the node from which you installed MapR, you must run the quick installer from the same node if you are performing an addition to an existing installation. Since new installations do not reference a manifest file,  you can perform new installations can from any node.

Quick Installer Configuration File

Installation with a configuration file is appropriate when:

  • You want to perform a non-interactive installation for speed or repetition.

  • The target nodes have different disk configurations.

  • You want to install an Apache ecosystem component like Spark or Hive.

To perform this type of installation, you must first create a configuration file. The example file, config.example, in the /opt/mapr-installer/bin directory shows the expected format of an installation configuration file.

# Each Node section can specify nodes in the following format
# Hostname: disk1, disk2, disk3
# Specifying disks is optional. If not provided, the installer will use the values of 'disks' from the Defaults section
#control-node1.mydomain: /dev/disk1, /dev/disk2, /dev/disk3
#control-node2.mydomain: /dev/disk3, /dev/disk9
#control-node3.mydomain: /dev/sdb, /dev/sdc, /dev/sdd
#data-node2.mydomain: /dev/sdb, /dev/sdc, /dev/sdd
#data-node3.mydomain: /dev/sdd
#data-node4.mydomain: /dev/sdb, /dev/sdd
MapReduce1 = false
YARN = true
HBase = false
MapR-DB = true
ControlNodesAsDataNodes = true
WirelevelSecurity = false
LocalRepo = false
ClusterName =
User = mapr
Group = mapr
Password = default_password
UID = 2000
GID = 2000
Disks = /dev/sdz
StripeWidth = 3
ForceFormat = false
CoreRepoURL =
EcoRepoURL =
Version = 4.0.1
MetricsDBHost =
MetricsDBUser =
MetricsDBPassword =
MetricsDBSchema =

#SparkVersion = 0.9.1
#SparkMasters = control-node1.mydomain, control-node2.mydomain
#SparkSlaves = data-node1.mydomain, data-node2.mydomain, data-node3.mydomain
#SparkMem = 2
#SparkWorkerMem = 1
#SparkDaemonMem = 16

#HiveVersion = 0.12
#HiveServers = control-node1.mydomain
#HiveMetaStore = control-node2.mydomain
#HiveClients = client-node1.mydomain, data-node3.mydomain

For a new installation, all sections must be present in the configuration file, although the [Data_Nodes] and [Client_Nodes] sections can be left empty. For additions to an existing installation, the [Control_Nodes][Data_Nodes], and [Client_Nodes] must be present, although they can be left empty. Other sections in the configuration file are silently ignored for additions.

The value of the Disks element of the [Defaults] section provides a fallback in the case where a node is specified in a previous [Control_Nodes][Data_Nodes], or [Client_Nodes] section without any disk information.

If the disks were used for a previous MapR installation, you must set ForceFormat to true.

ForceFormat reformats the disk, and any existing data will be permanently lost.

You do not have to specify values for the keys in the [Defaults] section, but each of the keys must be present.

Once the configuration file is created, you can initiate installation with one of the following commands.

sudo /opt/mapr-installer/bin/install -K -s --cfg /opt/mapr/bin/myconfigfile new
sudo /opt/mapr-installer/bin/install --cfg /opt/mapr/bin/myconfigfile new
sudo /opt/mapr-installer/bin/install --cfg /opt/mapr/bin/myconfigfile new

Installing Spark Using the Configuration File

To install Spark, uncomment and complete the configuration in the [Spark] section of the configuration file.  You must specify one or more hostnames to be SparkMaster nodes, which coordinate execution of Spark jobs, and one or more hostnames to serve as the SparkWorker nodes, which execute Spark jobs.  You can also modify the Spark memory configuration settings based on your environment.

Scala 2.10.3 or later is a pre-requisite for Spark installation. Verify that Scala is installed on nodes where you plan to install Spark.

Installing Hive Components using the Configuration File

To install Hive client and server components, uncomment and complete the configuration under the [Hive] section in the configuration file.  You may configure one or more hostnames on which to install the Hive clients, typically the same hostnames as specified in the [Clients] section.  One or more hostnames can also be provided for installation of HiveServer2, and a single hostname on which to install the Hive metastore. The Hive metastore will be configured to use the default Derby database.

Post Installation

To complete the post installation process, follow these steps:

  1. Access the MCS by entering the following URL in your browser, substituting the IP address with the IP address or hostname of a control node in your cluster:
    Compatible browsers include Chrome, Firefox 3.0 and above, Safari (see Browser Compatibility for more information), and Internet Explorer 10 and above. 

  2. If a message about the security certificate appears, click Proceed anyway.
  3. Log in with the MapR user name and password that you set during the installation.
  4. To register and apply a license, click Manage Licenses in the upper right corner, and follow the instructions to add a license via the web.
    See Managing Licenses for more information.
  5. Create separate volumes so you can specify different policies for different subsets of data. See Managing Data with Volumes for more information.
  6. Set up topology so the cluster is rack-aware for optimum replication. See Setting up Node Topology for more information. 


The Quick Installer fails with permissions errors: Many Ubuntu systems disable the root login for security reasons.

Resolution: Start the quick installer with the following options:

# sudo /opt/mapr-installer/bin/install -u <user> -s -U root [--sudo-password <password> | --ask-sudo-pass] new

You must use either the --sudo-password or the --ask-sudo-pass option. The --sudo-password option requires you to type the sudo password in the command line. The --ask-pass option requests the sudo password interactively.


The Quick Installer fails to format disks: The installer detected a previous installation of MapR software and displays a message similar to this:

  Configuring Disks for MapR File System
  Failed to format /dev/sdb,/dev/sdc,/dev/sdd for MapR FS.  Check
  /opt/mapr/logs/disksetup.0.log.  Please re-run the installer after addressing the
  reported issue(s).

Resolution: Select the ForceFormat option from the modify menu and set the value to true. Next, select continue to run the quick installer again. You can also edit the config.example file and change the value for ForceFormat to true, then run the installer.

Client disconnection disrupts my installation processTo prevent issues with client disconnection from affecting the install process, run the MapR quick installer from a screen or tmux session.

Using the MapR Quick Installer on a cloud installation: Cloud computing services assign you a private key for use with your cloud computing nodes. Typically, private key files use the .pem extension. To use this private key with the MapR quick installer, verify that the permissions for the file are 0600 (-rw-------). You can use the chmod command to set the permissions, as in the following example:

$ chmod 0600 filename.pem

Once the file has the correct permissions, specify the path to the private key file with the --private-key option.

The installer hangs at the ‘Configuring MapR Services’ step: The installer reports its activity with output similar to the following example:

* 21:00:12 Detecting Operating System
* 21:00:13 Installing Prerequisite Packages for CentOS/RedHat
* 21:01:55 Detecting Operating System
* 21:01:57 Configuring Firewall for CentOS/RedHat
* 21:01:59 Creating MapR User
* 21:02:08 Installing and Configuring NTP Service
* 21:02:17 Installing OpenJDK Packages If Needed
* 21:03:04 Detecting Operating System
* 21:03:06 Initializing MapR Repository for CentOS/RedHat
* 21:03:50 Installing MapR Packages
* 21:06:00 Disabling MapR Services Until Configured
* 21:06:04 Configuring MapR Services

One potential cause of this error condition is that the MapR user specified already exists on one of the nodes. In this case, the installer does not overwrite the credentials for that existing user and cannot authenticate to that node.

Resolution: Examine the log files to determine the precise cause of the error.

The apt-get utility fails with a ‘cannot get lock’ error message: The MapR Quick Installer requires root privileges. When root privileges are not available, this error message can result.

Resolution: Check the sudo or sudo-user settings on the cluster nodes, then run the MapR Quick Installer with the -u <user> -s -U root -K new flags, as in the following example:

# sudo /opt/mapr-installer/bin/install -u <user> -s -U root -K new