This is documentation for MapR Version 5.0. You can also refer to MapR documentation for the latest release.

Versions Compared

Key

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

...

Installation

MapReduce Classic

YARN

Mixed-Mode

Packages to install
on all cluster nodes

mapr-fileserver

mapr-fileserver

mapr-fileserver

Packages to install on
designated cluster nodes

mapr-cldb

mapr-zookeeper

mapr-nfs

mapr-webserver

mapr-metrics

mapr-gateway

mapr-jobtracker

mapr-tasktracker

mapr-cldb

mapr-zookeeper

mapr-nfs

mapr-webserver

mapr-metricsmapr-gateway

mapr-resourcemanager

mapr-nodemanager

mapr-historyserver


mapr-cldb

mapr-zookeeper

mapr-nfs

mapr-webserver

mapr-metrics

mapr-gateway

mapr-jobtracker

mapr-tasktracker

mapr-resourcemanager

mapr-nodemanager

mapr-historyserver

Package to install
on client machines that
run hadoop commands

mapr-clientmapr-clientmapr-client

...

  • Note the hostnames of the CLDB and ZooKeeper nodes. Optionally, you can specify the ports for the CLDB and ZooKeeper nodes as well. The default CLDB port is 7222. The default ZooKeeper port is 5181.
  • If a node in the cluster runs the HistoryServer, note the hostname for the HistoryServer. The HistoryServer node must be specified using the -HS parameter. 

  • If one or more nodes in the cluster runs the ResourceManager, note the hostname or IP address for each ResourceManager node. Based on the version you install and your ResourceManager high availability requirements, you may need to specify the ResourceManager nodes using the -RM parameter. Starting in 4.0.2, high availability for the ResourceManager is configured by default and does not need to be specified. For more information, see ResourceManager High Availability.

  • If mapr-fileserver is installed on this node, you can use configure.sh to format the disks and setup partitions or you can manually run disksetup after you run configure.sh. For more information, see Using configure.sh to Run disksetup.

  • For a cluster node that is on a VM, use the --ipvm parameter when you run configure.sh, so that the script uses less memory.

  • Starting in MapR version 4.0.1, the MapR Community Edition and the MapR Enterprise Database Edition licenses both provide read/write access to MapR-DB tables. The MapR Enterprise Edition license provides read-only access to MapR-DB tables. If you do not plan to access MapR-DB on your cluster, run configure.sh with the -noDB parameter on each node. This results in less memory being allocated to MFS, and more memory being allocated to MapReduce services.

...