MapR 5.2 is at End of Life (EOL) and no longer supported. Please see the latest documentation. This documentation is not being updated.

Home
5.2 Installation
This section contains information on installing and upgrading MapR. It also contains information on how to migrate data and applications from an Apache Hadoop cluster to a MapR cluster.
Upgrading MapR or MEP Components
Depending on your current configuration, you may choose to upgrade the MapR version (MapR Core), ecosystem components, clients, or MapR Monitoring components.
Upgrading MapR Expansion Packs
Describes how to upgrade MapR Expansion Packs (MEP), either as part of a MapR Core upgrade or to take advantage of a new MEP for the current version of MapR Core.
Finishing the MEP Upgrade
Complete the post-upgrade steps for each ecosystem component that was upgraded.
Post-Upgrade Steps for Storm
Complete the following steps after you upgrade Storm with or without the MapR Installer.

MapR 5.2 Documentation

5.2 Installation
This section contains information on installing and upgrading MapR. It also contains information on how to migrate data and applications from an Apache Hadoop cluster to a MapR cluster.
- Installing MapR or MEP Components
  Describes how to install MapR software and MapR Expansion Pack (MEP) components with the MapR Installer or without the MapR Installer.
- Installing MapR-XD
  Describes how to install MapR-XD software with or without the MapR Installer.
- Installing MapR in the Cloud
  Provides an overview of MapR cloud installer capabilities.
- Upgrading MapR or MEP Components
  Depending on your current configuration, you may choose to upgrade the MapR version (MapR Core), ecosystem components, clients, or MapR Monitoring components.
  - Upgrading MapR Core
    Describes the process of upgrading MapR Core.
  - Upgrading MapR Expansion Packs
    Describes how to upgrade MapR Expansion Packs (MEP), either as part of a MapR Core upgrade or to take advantage of a new MEP for the current version of MapR Core.
    - Planning MapR Expansion Pack (MEP) Upgrades
      The set of Ecosystem components that you run in the cluster must all belong to the same MEP.
    - Preparing to Upgrade the MEP
      Complete these pre-upgrade steps for each component in the MapR Expansion Pack (MEP) that you want to upgrade.
    - Upgrading the MEP With the MapR Installer
      If the cluster that you want to upgrade was installed using the MapR Installer, you can use the MapR Installer to upgrade the MapR Expansion Pack (MEP).
    - Upgrading the MEP Without the MapR Installer
      After you upgrade MapR core without using the MapR Installer, you need to upgrade ecosystems components with manual steps. First, verify that your repository is configured to use a MapR Expansion Pack (MEP) that is supported by your cluster version. Then, upgrade each component manually.
    - Finishing the MEP Upgrade
      Complete the post-upgrade steps for each ecosystem component that was upgraded.
      - Post-Upgrade Steps for Drill
        Complete the steps below after you upgrade Drill with or without the MapR Installer.
      - Post-Upgrade Steps for Flume
        Complete the following steps after you upgrade Flume with or without the MapR Installer.
      - Post-Upgrade Steps for HBase
        Complete the following steps after you upgrade HBase with or without the MapR Installer.
      - Post-Upgrade Steps for Hive
        Complete the following steps after you upgrade Hive with or without the MapR Installer.
      - Post-Upgrade Steps for HttpFS
        Complete the following steps after you upgrade HttpFS with or without the MapR Installer.
      - Post-Upgrade Steps for Hue
        Complete the following steps after you upgrade Hue with or without the MapR Installer:
      - Post-Upgrade Steps for Impala
        Complete the following steps after you upgrade Impala with or without the MapR Installer.
      - Post-Upgrade Steps for Mahout
        Complete the following steps after you upgrade Mahout with or without the MapR Installer.
      - Post-Upgrade Steps for MapR Monitoring
        Complete the following steps after you upgrade MapR Monitoring Components with or without the MapR Installer.
      - Post-Upgrade Steps for Oozie
        Complete the following steps after you upgrade Oozie with or without the MapR Installer.
      - Post-Upgrade Steps for Pig
        Complete the following steps after you upgrade Pig with or without the MapR Installer.
      - Post-Upgrade Steps for Sentry
        Complete the following steps after you upgrade Sentry with or without the MapR Installer.
      - Post-Upgrade Steps for Spark
        Complete the following steps after you upgrade Spark with or without the MapR Installer.
      - Post-Upgrade Steps for Sqoop1
        Complete the following steps after you upgrade Sqoop1 with or without the MapR Installer.
      - Post-Upgrade Steps for Sqoop2
        Complete the following steps after you upgrade Sqoop2 with or without the MapR Installer.
      - Post-Upgrade Steps for Storm
        Complete the following steps after you upgrade Storm with or without the MapR Installer.
      - Post-Upgrade Steps for Tez
        Complete the following steps after you upgrade Tez with or without the MapR Installer.
- Migrating to MapR
  Provides instructions for migrating business-critical data and applications from an Apache Hadoop cluster to a MapR cluster.
- Applying a Patch
  You can apply a patch by using the MapR Installer, by using the command line (a manual process), or by using a MapR Installer Stanza.

Post-Upgrade Steps for Storm

Complete the following steps after you upgrade Storm with or without the MapR Installer.

About this task

Procedure

Stop all Storm services.
1. Make a list of nodes on which Storm is configured (including the nimbus daemon and the supervisor daemons).
2. Run these commands on each node where Storm is configured:
```
/opt/mapr/storm/storm-<version>/bin/storm-daemon.sh stop supervisor
/opt/mapr/storm/storm-<version>/bin/storm-daemon.sh stop nimbus
/opt/mapr/storm/storm-<version>/bin/storm-daemon.sh stop core
```
Clean the tmp directory.
```
 rm -rf /tmp/storm-data/*
```
Migrate Custom Configurations.
When you upgrade to a newer Storm version, a new storm-<version> folder is created, and the old configuration files are not automatically migrated to the new folder. Migrate any custom configuration settings into the new default files in the conf directory (/opt/mapr/storm/storm-<version>/conf/).

Start Storm services on each node where Storm is configured.

maprcli node services -name nimbus -action start -nodes <space delimited list of nodes>
maprcli node services -name storm-ui -action start -nodes <space delimited list of nodes>
maprcli node services -name supervisor -action start -nodes <space delimited list of nodes>

Resubmit the topology:
```
storm jar <jar-path> <main class>
```