How the MapR Installer Works

This topic provides steps for setting up and running the MapR Installer.

Before you can run the MapR Installer, you must run the mapr-setup.sh script to set up the installation environment on a node that will be part of the cluster. Then, you can run the MapR Installer to perform the installation.

See the following topics for more information:

mapr-setup.sh

The mapr-setup.sh script performs the following steps to prepare the node to run the MapR Installer:

  1. Verifies and installs the operating system dependencies and Java requirements on the current node.
  2. Checks for Internet connectivity.

    If access to package.mapr.com is not available, the script prompts for archive files.

  3. Asks for the hostname and port that cluster nodes can use to connect to the MapR Installer node.
  4. Asks for the cluster admin user account and creates the account if it does not exists. This account must exist or be created on each node in the cluster.
  5. Creates a repository with the required package file.
    • If no archive file is provided, it configures access to the package.mapr.com repository. For example, on RedHat / CentOS it creates the following repository: /etc/yum.repos.d/mapr.installer.repo

    • If archive files are provided, it sets up a local repository with the all the packages in the specified archive TAR files.

Syntax
/opt/mapr-installer/bin/mapr-setup.sh 
[-a <full_path_to_archive_file(s)>]
[-p <hostname:port>]
Options
Option Description
-a When you want the mapr-setup.sh to bypass the Internet connectivity check and directly create a local repository instead of an Internet repository, specify a space delimited list of the full paths to the following archive files:
  • MapR Installer archive
  • MapR Ecosystem Pack (MEP) archive
  • MapR 5.2 archive
For more information, see Using a Local, Shared Repository With the MapR Installer
-p The hostname:port to use for installation-related communication between the MapR Installer node and other nodes in the cluster. The MapR Installer also adds the hostname provided as a default entry for the list of cluster nodes on the Configure Nodes page. Both the hostname and the port are not required when configuring this option; you can choose to configure one or both values.
Note: Configure this option when the MapR Installer node has multiple interfaces or hostnames and the result of `hostname` is not a value that other nodes in the cluster are able to communicate with.

MapR Installer Web Interface

When you run the MapR Installer, it performs the following tasks:

  1. Displays the MapR services and ecosystem components that you can install based on the MapR version that you select.
  2. Provides the option to install MapR Monitoring.
  3. Guides you through node and cluster configuration.
  4. Verifies that each node meets the node requirements.
  5. Sets a default, configurable service layout across the nodes in the cluster based on the requirements of each service.
  6. Installs or upgrades the MapR software and associated operating system dependencies.
  7. If you chose to install a trial or community license, it will attempt to apply the license to your cluster.

MapR Installer Components

The MapR Installer uses the following components to set up the installation environment:

Name Filename Description
Configuration Script mapr-setup.sh Script that configures a node to run the MapR Installer. This includes setting up an Internet or local repository.
Installer Package mapr-installer-<version> Package that contains the MapR Installer.
Installer Definitions Package mapr-installer-definitions-<version> Package that contains the list of MapR versions, services, and ecosystem components that you can install with the MapR Installer.
MapR Service Packages various

If you use an Internet repository, the MapR Installer accesses the installation packages from package.mapr.com.

If you use a local repository, the MapR Installer accesses the installation packages from the local repository. The mapr-setup.sh script creates the local repository with the packages available in the archive files that you provide to the mapr-setup.sh script. For more information, see Using a Local, Shared Repository With the MapR Installer