HPE Ezmeral Data Fabric 6.1.x is In Maintenance and transitions to "End of Maintenance" in June 2024. Please see the latest documentation.

About MapR 6.1
This site contains the main documentation for Version 6.1 of the MapR Converged Data Platform, including installation, configuration, administration, and reference information.
6.1 Installation
This section contains information about installing and upgrading MapR software. It also contains information about how to migrate data and applications from an Apache Hadoop cluster to a MapR cluster.
- Planning the Cluster
  Describes information and factors used in planning your cluster.
- Installing MapR and MapR Ecosystem Components
  Describes how to install MapR software and ecosystem components with or without the MapR Installer.
- Installing the File Migration Service on the Edge Cluster
  Describes how to install the File Migration service on CentOS nodes.
- Installing the MapR XD Distributed File and Object Store
  Describes how to install MapR XD software with or without the MapR Installer.
- Installing MapR Data Fabric for Kubernetes
  This section describes how to plan for and install the MapR Container Storage Interface (CSI) Storage Plugin and the MapR Data Fabric for Kubernetes FlexVolume Driver.
- Installing MapR in the Cloud
  Provides an overview of MapR cloud installer capabilities.
- Installing Metering
  This section describes how to install Metering by using the MapR Installer or manual steps.
- Upgrading MapR Core or EEP Components
  Depending on your current configuration, you may choose to upgrade the release version (core), ecosystem components, clients, or monitoring components.
  - Upgrade Workflows
    This section describes three common methods for upgrading from one MapR core release to another. The workflows in this section introduce you to the high-level steps for each method and provide links to pages showing more detail.
  - Upgrading MapR Core
    Describes the process of upgrading MapR core.
  - Upgrading Ezmeral Ecosystem Packs
    Describes how to upgrade Ezmeral Ecosystem Packs (EEPs), either as part of a MapR core upgrade or to take advantage of a new EEP for the current version of MapR core.
    - Planning Ezmeral Ecosystem Pack (EEP) Upgrades
      The set of ecosystem components that you run in the cluster must all belong to the same EEP.
    - Preparing to Upgrade the Ezmeral Ecosystem Pack
      Complete these pre-upgrade steps for each ecosystem component in the EEP that you want to upgrade.
      - Pre-Upgrade Steps for Drill
        Complete the following steps before you upgrade Drill with or without the MapR Installer.
      - Pre-Upgrade Steps for Flume
        Complete the following steps before you upgrade Flume with or without the MapR Installer.
      - Pre-Upgrade Steps for HBase
        Complete the following steps before you upgrade HBase with or without the MapR Installer.
      - Pre-Upgrade Steps for HBase Client
        Complete the following steps before you upgrade HBase Client with or without the MapR Installer.
      - Pre-Upgrade Steps for Hive
        Complete the following steps before you upgrade Hive with or without the MapR Installer.
      - Pre-Upgrade Steps for HttpFS
        Complete the following steps before you upgrade HttpFS with or without the MapR Installer.
      - Pre-Upgrade Steps for Hue
        Complete the following steps before you upgrade Hue with or without the MapR Installer.
      - Pre-Upgrade Steps for Impala
        Complete the following steps before you upgrade Impala with or without the MapR Installer.
      - Pre-Upgrade Steps for MapR Data Access Gateway
        Complete the following steps before you upgrade the MapR Data Access Gateway with or without the MapR Installer.
      - Pre-Upgrade Steps for Livy
      - Pre-Upgrade Steps for MapR Monitoring
        Complete the following steps before you upgrade MapR Monitoring Components with or without the MapR Installer.
      - Pre-Upgrade Steps for MapR Object Store with S3-Compatible API
        Complete the following steps before you upgrade the MapR Object Store with S3-Compatible API with or without the MapR Installer.
      - Pre-Upgrade Steps for MapR Event Store For Apache Kafka Tools
        Complete the following steps before you manually upgrade MapR Event Store For Apache Kafka Tools.
      - Pre-Upgrade Steps for Oozie
        Complete the following steps before you upgrade Oozie with or without the MapR Installer.
      - Pre-Upgrade Steps for Pig
        Complete the following steps before you upgrade Pig with or without the MapR Installer.
      - Pre-Upgrade Steps for Sentry
        Complete the following steps before you upgrade Sentry with or without the MapR Installer.
      - Pre-Upgrade Steps for Spark
        Complete the following steps before you upgrade Spark with or without the MapR Installer.
      - Pre-Upgrade Steps for Sqoop1
        Review the following information before you upgrade Sqoop1 with or without the MapR Installer.
      - Pre-Upgrade Steps for Sqoop2
        Complete the following steps before you upgrade Sqoop2 with or without the MapR Installer.
      - Pre-Upgrade Steps for Tez
        Complete the following steps before you upgrade Tez with or without the MapR Installer.
    - Upgrading the Ezmeral Ecosystem Pack 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 Ezmeral Ecosystem Pack (EEP).
    - Upgrading the Ezmeral Ecosystem Pack Without the MapR Installer
      After you upgrade MapR core without using the MapR Installer, you need to upgrade ecosystem components with manual steps. First, verify that your repository is configured to use an Ezmeral Ecosystem Pack (EEP) that is supported by your cluster version. Then, upgrade each component manually.
    - Finishing the Ezmeral Ecosystem Pack Upgrade
      Complete the post-upgrade steps for each ecosystem component that was upgraded.
  - Preparing the Cluster for a Maintenance Update
    This section identifies how to prepare for applying either a minor update or a patch.
  - Performing a Maintenance Update
    Perform a maintenance update when you want to upgrade to a new patch version of MapR core or apply a patch.
- Setting Up Clients and Services
  Describes how to set up and use interfaces to an cluster from a client computer.
- Setting Up the Control System
  Describes how to configure and access the Control System.
- 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 an Installer Stanza.
6.1 MapR Data Platform
MapR Data Platform is the industry-leading data platform for AI and analytics that solves enterprise business needs.
6.1 Administration
This section describes how to manage the nodes and services that make up a cluster.
6.1 Development
This section contains information related to application development for Ezmeral ecosystem components and MapR Data Platform products, including the file system, Database (Key-Value and JSON), and Event Streams.
Other Docs
This section contains release-independent information, including: MapR Installer documentation, Ecosystem release notes, interoperability matrices, security vulnerabilities, and links to other MapR version documentation.
Glossary
Definitions for commonly used terms in MapR Converged Data Platform environments.

Pre-Upgrade Steps for Spark

Complete the following steps before you upgrade Spark with or without the MapR Installer.

Pre-Upgrade Steps for Spark Standalone

About this task

Procedure

Copy configuration files from /opt/mapr/spark/spark-<version>/conf to a location outside of the MapR installation directory.
For example, if Spark SQL is configured to work with Hive, copy the /opt/mapr/spark/spark-<version>/conf/hive-site.xml file to a backup directory.

Shut down the spark-master, spark-historyserver services (if the spark-historyserver is running).

maprcli node services -nodes <node-ip> -name spark-master -action stop
maprcli node services -nodes <node-ip> -name spark-historyserver -action stop

As the mapr user, stop the secondary instances:
For Spark 2.x:
```
/opt/mapr/spark/spark-<version>/sbin/stop-slaves.sh
```
For Sparx 3.x:
```
/opt/mapr/spark/spark-<version>/sbin/stop-workers.sh
```

Pre-Upgrade Steps for Spark on YARN

Procedure

Copy configuration files from /opt/mapr/spark/spark-<version>/conf to a location outside of the MapR installation directory.
For example, if Spark SQL is configured to work with Hive, copy the /opt/mapr/spark/spark-<version>/conf/hive-site.xml file to a backup directory.
Shut down the spark-historyserver services (if the spark-historyserver is running):
```
maprcli node services -nodes <node-ip> -name spark-historyserver -action stop
```

Preserving Spark Configuration

About this task

Starting from EEP 6.0.0, in case of a version update, configuration from a previously installed version of Spark is stored in a folder with an old version timestamp.