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.
Planning MapR Expansion Pack (MEP) Upgrades
The set of Ecosystem components that you run in the cluster must all belong to the same MEP.

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.
- 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.

Planning MapR Expansion Pack (MEP) Upgrades

The set of Ecosystem components that you run in the cluster must all belong to the same MEP.

As of MapR 5.2, you must upgrade to the MEP path. You will be offered packs to install that contain selected component versions. After upgrading, you may want to upgrade to a more recent MEP to get the latest patch releases or newer versions of ecosystem components.

While each MapR core version may be supported by more than one MEP, the set of ecosystem components that you run in the cluster must all belong to the same MEP. You cannot selectively upgrade components. When you upgrade a MEP, all components are replaced with the versions contained in the newly selected MEP.

For details on the ecosystem components available in each MEP and the list of MEPs supported by your MapR cluster version, see:

For API or behavioral changes associated with new ecosystem components, see the documentation for the individual component under Ecosystem Components.