MapR Installer Prerequisites and Guidelines
The node on which you run the MapR installer and the nodes you plan to include in your MapR cluster must meet the following requirements.
It must be one of the nodes you plan to install the cluster on.
Ensure that the default umask for the root user is set to
Based on the operating system, it requires the following packages:
It must have JDK 1.7 or higher.
If JDK 1.7 or higher is unavailable, mapr-setup.sh will install OpenJDK.
|SSH Access||It must have SSH access to all nodes that you want to include in the cluster.|
|Port Availability||Port 9443 or the non-default port that you configure using
- Google Chrome
For more information, see the Interoperability Matrix.
Nodes that you want to include in the cluster must meet the following criteria:
- They are configured to accept operating system and security updates. They must also be patched with the latest security fixes. See your operating system vendor’s documentation for details.
- They meet the requirements listed in Preparing Each Node. The MapR Installer will verify the requirements prior to installation.
- They have HTTPS access to the MapR Installer node over port 9443.
When you specify the nodes in the MapR Installer, the nodes must also be defined by resolvable hostnames or static IP addresses.
If nodes in the cluster use an HTTP proxy server, the nodes must also meet the following requirements:
The no_proxy environment variable must be set.
Nodes in the MapR cluster need to be able to communicate without the use of a proxy. If the https_proxy and http_proxy environment variable is set for nodes in the cluster, you must also set the no_proxy environment variable for the MapR admin user and the root user on each node. Configure the no_proxy environment variable to the IP range of the MapR nodes or to the sub-domain that contains the MapR nodes.
In addition, you must follow this guideline from the Python documentation: "The
no_proxyenvironment variable can be used to specify hosts which shouldn't be reached via proxy; if set, it should be a comma-separated list of hostname suffixes, optionally with
:portappended, for example
The global proxy for package repositories must be set.MapR Installer creates repository files. However, the proxy setting are not configured for each repository. Therefore, configure global proxy settings on each node in the cluster.
- On CentOS/RedHat, set global proxy settings in /etc/yum.conf.
- On Ubuntu, set global proxy settings in /etc/apt/apt.conf.
Using the MapR Installer on Nodes in the Cloud
When you run the MapR Installer on nodes in the cloud, note the following points:
Verify that port 9443 is open.
The MapR Installer requires that this port is available.
The MapR Installer and service UI URLs should refer to an external URL not an internal URL.
For example, when you open the MapR installer URL, replace any internal hostname or IP address with its associated external address. For Amazon EC2 and Google Compute Engine (GCE) clusters, the MapR Installer automatically translates internal addresses to external addresses.
- On the Configure Nodes page of the MapR Installer web interface, make sure that you
do the following:
- Define each node with internal static IP addresses or internal resolvable hostnames.
- For the remote authentication, use the same user ID and private key that you use to
ssh into your cloud instances. This user must be
rootor a user with