- Select a node to run the MapR Installer.
The node from which you run the MapR Installer must also be one of the nodes you plan to install the cluster on. Before you begin, you may want to check the prerequisites and known limitations.
- Download the mapr-setup.sh script.
Download mapr-setup.sh from mapr.com. Then, copy mapr-setup.sh to the node that will run the MapR Installer.
Run the mapr-setup.sh script to configure the node to run the MapR Installer.
Run the following command as the
root user from the directory that contains the script:
- Start the MapR Installer.
Open the MapR Installer URL:
https://<MapR Installer Node hostname/IPaddress>:9443
You will be prompted to log in as the MapR Administrator user that you configured while running the
The MapR Installer installs MapR software after it walks you through the process of selecting services and configuring the cluster.
Once the installation completes, you can use the same MapR Installer URL to perform the following:
- Use the Incremental Install option to add nodes, add services, and upgrade services that are already installed on the cluster.
- Use the Upgrade option to upgrade the cluster to a newer MapR version and upgrade services that are already installed on the cluster. For more information, see Upgrading with the MapR Installer.
|The MapR Installer definitions are updated frequently. You may need to update the MapR Installer to get the latest ecosystem components and MapR versions.|
|title||Install on Nodes in the Cloud |
When you run the MapR Installer on nodes in the cloud, note the following points:
- 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
root or a user with
Based on the cluster requirements and firewall restrictions, you may need to open the following types of ports for external access:
- Ports used by user interfaces such as the MCS, Resource Manager UI, JobTracker UI.
- Ports used by clients such as Hive, Impala, Drill, and Spark-SQL.
- Ports used by MapR client machines to access the MapR-FS or to run hadoop jobs.
See Ports Used by MapR for a list of ports.
|title||Install using a Local, Shared Package Repository|
When you run the
mapr-setup.sh script, it attempts to connect to package.mapr.com and configures an Internet repository. If there is no Internet connectivity, the script asks for the archive file so that it can create a local repository. The archive file contains all the installation packages that are available on package.mapr.com at the time at which you download it.
-a <full path to archive file> to
mapr-setup.sh script bypasses the Internet connectivity check and automatically creates a local repository with the provided archive file.
To install with a local,shared repository, the node that runs
mapr-setup.sh needs the following:
- Any OS dependencies or Java Development Kit (JDK) packages that are required.
- A webserver.
The script will attempt to install a webserver on the node if a webserver is not available. The webserver is needed to provide the MapR package files to each node in the cluster.
- The following items in a directory on the node:
- mapr-latest-<version>.<dep|rpm>.tar.gz (archive file)
Based on the operating system of the node, download the archive file from one of the following locations:
After downloading the mapr-setup.sh script and the archive file to the node that will run the MapR Installer, run the following command from the directory that contains the mapr-setup.sh script:
bash ./mapr-setup.sh –a <full path to the archive file>
|title||MapR Installer Requirements|
The node the runs the MapR Installer must meet the following requirements:
It must be one of nodes you plan to install the cluster on.
Ensure that the default umask for the root user is set to 0022 on all mapr nodes in the cluster. The umask setting is changed in the /etc/profile file, or in the .cshrc or .login file. The root user must have a 0022 umask because the MapR admin user requires access to all files and directories under the /opt/mapr directory, even those initially created by root services.
Based on the operating system, it requires the following packages:
- On Ubuntu nodes:
- On Red Hat/ CentOS nodes:
|If not found, the mapr-setup.sh utility will attempt to download these packages from internet repositories.|
It must have JDK 1.7 or higher.
If JDK 1.7 or higher is unavailable, mapr-setup.sh will install OpenJDK.
- On RedHat/CentOS, mapr-setup.sh installs Open JDK Java 1.8.
- On Ubuntu, mapr-setup.sh installs Open JDK Java 1.7.
|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 mapr-setup.sh must be accessible on the MapR Installer node to all nodes that you want to include in the cluster.|
Once the MapR Installer is installed and configured, the following web browsers can be used to access the MapR Installer web interface:
• 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.
- 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.
- See the MapR Installer video for an overview of the steps and options available when you configure and run the MapR Installer.
- See the How the MapR Installer Works for information about the mapr-setup.sh script and the MapR Installer.
- See the Frequently Asked Questions section for additional information and troubleshooting.
more information, see Using the MapR Installer.