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.
    - Step 1: Verify Cluster Readiness for a Patch
      Before you apply a patch, check that the cluster is ready for a patch to be applied. In addition to the prerequisites, consider verifying that the cluster utilizes best practices which will facilitate a more optimal patch installation.
    - Step 2: Apply the Patch to Data Nodes
      When applying a patch manually, apply the patch to nodes dedicated to storing and processing data prior to applying the patch to nodes that run the CLDB. This includes nodes that run the Fileserver for storage and processing components such as the NodeManager and the HBase client.
    - Step 3: Apply the Patch to CLDB Nodes
      When applying a patch manually, apply the patch to CLDB secondary nodes prior to applying the patch on the primary CLDB node. After you apply a patch to a CLDB node, you must verify that container 1 is fully replicated before proceeding to apply the patch to the next CLDB node.
  - 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 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.

Before applying a patch, note these considerations:

For patch-download information, see Applying a Patch.
The steps for patching the Control System are different from the steps for patching MapR core. See Special Considerations for the Control System Patches.
You can also apply a patch using the MapR Installer. See Applying a Patch Using the MapR Installer.
A patch for a given software version can be removed, and an older patch for the same MapR software version can be installed. However, rolling back a cluster from a newer release version to an older version is not supported.

Different types of patches are available, and some patches can only be installed on specific nodes:

Patch Type	Install on These Nodes
`mapr-patch`	All control and data nodes
`mapr-patch-client`	MapR client nodes only
`mapr-patch-loopbacknfs`	Any node where POSIX is supported
`mapr-patch-nfs4server`	Any node where NFSv4 is supported
`mapr-patch-posix-client-basic`	Any node where FUSE POSIX is supported
`mapr-patch-posix-client-platinum`	Any node where FUSE POSIX is supported

Applying a patch is a three-step process:

When you apply a patch to the cluster, the patched files along with original files (non-patched) are copied to the /opt/mapr/.patch folder. In the /opt/mapr/.patch folder, the file ending with .O is the original file (non-patched) and the file ending with .<patch_number> is the patched version. Therefore, if there is a file under /opt/mapr/.patch/lib/, you can compare that with the corresponding file under /opt/mapr/lib/ by using the md5sum command to verify that the patch was successfully deployed.

If you need more information or if you encounter any problems with patch installation, contact HPE Support.