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.
- 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.
  - Downloading a Patch
    MapR patches can be downloaded from a secure FTP server.
  - Applying a Patch Using the MapR Installer
    The MapR Installer automates much of the work involved in applying MapR patches.
  - Applying a Patch Manually
    MapR patches are version-specific and cumulative. Each patch contains the code fixes that were included in the previous patch for that release version.
  - Applying a Patch Using an Installer Stanza
    Applying a patch using an Installer Stanza leverages the automation provided by the patch-install capability of the web-based MapR Installer.
  - Rolling Back a Patch
    Removing a previously installed patch is a manual process. You can revert to a previous version of the patch by first removing the current patch and then installing the previous version.
  - Applying a Patch for an Ecosystem Component
    Patches for ecosystem components are handled differently from patches for MapR core software.
  - Special Considerations for the Control System Patches
    Patches for the Control System are handled differently from patches for cluster data nodes and CLDB nodes.
  - Special Considerations for FUSE POSIX Patches
    Patches for some features, such as the FUSE POSIX client, can require post-installation steps.
  - Applying a Patch to a MapR POSIX Client
    This procedure enables you to apply a patch to any of the MapR POSIX clients, which include the MapR loopbacknfs POSIX client, the FUSE-based POSIX basic client, and the FUSE-based POSIX platinum client.
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.

Applying a Patch for an Ecosystem Component

Patches for ecosystem components are handled differently from patches for MapR core software.

About Patches for Ecosystem Components

Ecosystem components are updated as a package rather than a patch file. While core patches typically include a prefix such as mapr-patch or mapr-patch-client, ecosystem patches are delivered as a new package and do not use the core patch mechanism.

To identify an ecosystem patch package, look for the component name in the patch name. For example:

mapr-livy-0.7.0.304.202309110421-1.noarch.rpm

Then use the steps on this page to update the currently installed package. The steps on this page use the Livy component as an example.

Downloading a Patch for an Ecosystem Component

Patches for ecosystem components can be downloaded from the secure FTP server. To download a patch file for an ecosystem component:

Use the steps in Downloading a Patch to sign in to the secure FTP server.
Navigate to the /ecosystem/rpm/<component-name>/ or /ecosystem/deb/<component-name>/ directory.
Click the patch to select it.
Click Download.

Applying the Patch

To apply the patch:

On all nodes where the ecosystem component is running, stop the service for the component. For example:
```
maprcli node services -name livy -action stop -nodes <ip_address>
```
Before upgrading, check to see if other actions are needed. For example, you might want to back up configuration files for a component before upgrading. For more information, review the pre-upgrade steps for the component in Preparing to Upgrade the Ezmeral Ecosystem Pack.
Use the following commands to upgrade the currently installed package for the component. For example:
- On RHEL / CentOS or SLES:
```
rpm -U <path to new package>
```
- On Ubuntu:
```
dpkg -i <path to new package>
```
Run configure.sh to update the configuration for the new package:
```
$ /opt/mapr/server/configure.sh -R --noRecalcMem
```
On all nodes where the service is installed, start the service:
```
maprcli node services -name livy -action start -nodes <ip_address>
```