Installation and Upgrade Notes (Release 6.2.0)

This page describes considerations for installing or upgrading to release 6.2.0.

Installing Release 6.2.0 (All Methods)

Note these considerations for new installations of release 6.2.0, which apply regardless of the method you use to install the release:
Hadoop and YARN Are Provided as Ecosystem Components Beginning with core 6.2.0 and MEP 7.0.0, Hadoop and YARN services are no longer included in the repository for core packages. They are provided as ecosystem components in the MEP repository. This enables Hadoop and YARN to be upgraded separately from the HPE Ezmeral Data Fabric. To decouple Hadoop and YARN from core, the mapr-mapreduce2 package was removed, and some new packages were added. For more information, see Installing Hadoop and YARN.
SUSE Support HPE Ezmeral Data Fabric 6.2.0 is supported on SUSE 15 SP2. For a complete list of supported operating systems, see Operating System Support Matrix (Release 6.x)
New MAPR_JMX Environment Variables and configure.sh options Release 6.2.0 implements new MAPR_JMX environment variables and server configure.sh options to address the following security vulnerabilities:These environment variables and configure.sh options give you greater control over security aspects of JMX monitoring. Note the following considerations for new installations and upgrades:
  • On a new installation of release 6.1, remote host is enabled. On a new installation of release 6.2, local binding is enabled. On an upgrade, both local binding and remote JMX are enabled.
  • On release 6.2, Collectd always uses local binding and ignores remote host or local host settings. If you enable local JMX, Collectd continues to collect metrics, and if you enable remote JMX, Collectd still is able to collect it. But if you disable JMX, then Collectd does NOT collect JMX metrics from the JMX-enabled services.
For more information, see Controlling Access to JMX Metrics.
Simplified Installation for Log Monitoring Release 6.2 simplifies the manual installation of log-monitoring files by adding new certificates. All the log-stack security keys and certificates are generated when you run the server configure.sh command with the -genKeys option during cluster configuration.

To configure log monitoring using the manual steps, see Step 9: Install Log Monitoring. To learn more about the new keystore and truststore files, see Understanding the Truststore and Keyfiles.

4-Digit Version Numbers for Core and Patches Beginning with release 6.2.0, core and patch versions have four digits. The fourth digit adds precision not only for core versions, but also for JAR files and Maven artifacts. For the core version, the fourth digit represents a patch version. Even though newer core versions have four digits, most references to core versions in this documentation use two or three digits.

For more information, see Understanding Software Versions.

Installing Release 6.2.0 Using the Installer

Note these considerations for new installations of release 6.2.0 using the Installer:
Enabling Package Repositories for SUSE 15 Before using the Installer for a new data-fabric installation on SUSE 15 SP2, run the following command on all nodes to enable the Python 2 package repository. You must also run the command on the Installer node if the Installer node is not part of the cluster and is running SUSE 15 SP2 (or a later supported service pack):

SUSEConnect -p sle-module-python2/15.<version>/x86_64

If you are developing applications on the cluster, run the following command on all nodes:

SUSEConnect -p sle-module-development-tools/15.<version>/x86_64

To view the available SUSE modules and learn how to enable or disable them, use the SUSEConnect -l command.

Ubuntu 16.04 Installations Require Manual Installation of JDK Before Using Installer Before using the Installer on Ubuntu 16.04 nodes, you must manually install the JDK. If you are using the latest Installer on RHEL/CentOS, the Installer installs OpenJDK 11 for you. For more information, see the Installer Prerequisites and Guidelines.
KMIP Installation Is Not Supported Using the Installer The Installer does not support installing or configuring the External KMIP Keystore functionality. If you want to use KMIP and you are performing a new installation using the Installer, you must first perform a regular installation. Then you must use the mrhsm utility to import the generated CLDB and DARE keys into the hardware security module (HSM), and copy the contents of the ${MAPR_HOME}/conf/tokens directory to all CLDB nodes in the cluster. For more information, see External KMIP Keystore Overview and Setting Up the External KMIP Keystore

Upgrading to Release 6.2.0 (High-Level Steps)

Depending on your current data-fabric release, upgrading to release 6.2.0 can require multiple steps. Upgrading to release 6.2.0 can require an OS upgrade and always requires a JDK upgrade. The following table summarizes the high-level upgrade steps:
If your cluster is running release Use these steps to upgrade to release 6.2.0 See for more information
6.1.0 or 6.1.1
  1. Upgrade your MEP to MEP 6.3.1 (or later MEP 6.3.x).
  2. Upgrade your OS to an OS that is supported by release 6.2.0. For example:
    • RHEL/CentOS 8.2 or 8.3
    • Ubuntu 18.04
    • Ubuntu 16.04
  3. Install Java JDK 11 or the equivalent.
  4. Upgrade from release 6.1.x to 6.2.0 using one of the upgrade workflows.
5.2.x or 6.0.x
  1. Upgrade to release 6.1.1 and MEP 6.3.1 (or later MEP 6.3.x) using the release 6.1 documentation. See Installation and Upgrade Notes (MapR 6.1). Then return to the upgrade information here to upgrade from release 6.1.1 to 6.2.0.
  2. Upgrade your OS to an OS that is supported by release 6.2.0. For example:
    • RHEL/CentOS 8.2 or 8.3
    • Ubuntu 18.04
    • Ubuntu 16.04
  3. Install Java JDK 11 or equivalent.
  4. Upgrade from release 6.1.1 to 6.2.0 using one of the upgrade workflows.

Upgrade Considerations (All Upgrade Methods)

Core and MEP Requirements for Upgrading Clusters to be upgraded to release 6.2.0 must be installed with release 6.1.0 or 6.1.1 and MEP 6.3.1 (or later MEP 6.3.x) before upgrading, as indicated in the high-level upgrade steps earlier on this page. If your cluster is on release 5.2.x or 6.0.x, you must first upgrade to release 6.1.x and MEP 6.3.1 (or later MEP 6.3.x).
Upgrades to Red Hat / CentOS 8.1 Upgrades from Red Hat / CentOS 7.x to Red Hat / CentOS 8.1 are not supported. To take advantage of the new features in release 6.2.0 by way of an upgrade, you must upgrade to Red Hat / CentOS 8.2 or 8.3. For more information about OS upgrade paths, see the Red Hat documentation.
NFSv4 Upgrade Restrictions NFSv4 is not supported on release 6.1.x clusters on CentOS 8.2. Because of this restriction, a fresh install of release 6.1.0 on CentOS 8.2 is not supported for clusters using NFSv4. An OS-only upgrade from CentOS 7.x to release 6.1.x on CentOS 8.2 also is not supported.
To support NFSv4 on CentOS 8.2, a 6.1.x cluster must be upgraded to release 6.2 using one of the following procedures:
  • NFSv4 Gateway-Only Node
    1. Stop NFSv4 on the node.
    2. Upgrade the OS to CentOS 8.2 and the DF to release 6.2.
    3. Restart NFSv4 on the node.
  • NFSv4 Data Node
    1. Stop everything on the node.
    2. Upgrade the OS to CentOS 8.2 and the DF to release 6.2.
    3. Bring the node back up.
Hadoop and YARN Are Provided as Ecosystem Components Beginning with core 6.2.0 and MEP 7.0.0, Hadoop and YARN services are no longer included in the repository for core packages. They are provided as ecosystem components in the MEP repository. If you are upgrading and need Hadoop and YARN services, you must install the packages as ecosystem components after upgrading. For more information, see Installing Hadoop and YARN.
Data-on-wire-encryption Beginning with release 6.1, data-on-wire encryption is enabled by default for newly created volumes on secure clusters. Data-on-wire encryption encrypts data in a volume during transmission over the wire. Data-on-wire encryption is not supported for non-secure clusters.

When you upgrade a cluster to a release 6.1.x secure cluster, data-on-wire encryption is enabled by default. You can disable data-on-wire encryption for individual volumes using the Control System, the maprcli, or REST API commands.

Release 6.2.0 and MEP 7.0.0 Release 6.2.0 requires MEP 7.0.0 or later. For more information, see MEP Support and Lifecycle Status.
Regenerating the mapruserticket File Changes to the CanImpersonate parameter of the mapruserticket file in release 6.1.0 require users who upgrade manually to regenerate the file before restarting Warden. See Step 1: Restart and Check Cluster Services.

The file needs to be regenerated to ensure that impersonation works correctly for non-mapr users. Prior to release 6.1.0, all mapruserticket files were generated with CanImpersonate = false. Release 6.1.0 and later enforce the CanImpersonate parameter and sets the parameter to true for freshly installed clusters. For upgraded clusters, if CanImpersonate is not set to true, some services will not be able to impersonate.

Enabling PBS If you are upgrading from a data-fabric version that does not support extended attributes, you must enable extended attributes before you enable policy-based security (PBS):
/opt/mapr/bin/maprcli cluster feature enable -name mfs.feature.
fileace.support
To enable PBS:
/opt/mapr/bin/maprcli cluster feature enable -name mfs.feature.pbs

For more information, see Step 4: Enable New Features and Policy-Based Security.

Professional Support for Upgrades Upgrading can be time-consuming and complicated. Consider engaging HPE professional support services to assist in planning and executing your upgrade. For more information, contact your support representative.

Upgrade Considerations (Installer Upgrades)

Note these considerations for using the MapR Installer to upgrade to release 6.2.0:

Installer 1.14.0 Before upgrading, update the MapR Installer to version 1.14 or later. Installer 1.14 is compatible with earlier data-fabric releases and MEPs, and only Installer 1.14 or later can be used with data-fabric release 6.2.0 and MEP 7.0.0.
Most Upgrades to Release 6.2.0 Require an OS Upgrade The Installer version upgrade feature can upgrade the data-fabric core version, the Java version, and ecosystem components. However, the Installer does not upgrade the OS version.

In most cases, upgrading to core 6.2.0 requires an OS upgrade. For example, if your cluster is installed with core 6.1.0 running on CentOS 7.8, you must upgrade the OS to CentOS 8.2 before using the Installer to upgrade data-fabric software to core 6.2.0. See When Upgrading Core with the Installer Requires an OS Upgrade.

You can use the Installer to upgrade directly to core 6.2.0 ONLY if your cluster is running an OS version that core 6.2 supports. These OS versions currently include:
  • Red Hat / CentOS 8.2
  • Ubuntu 18.04
  • Ubuntu 16.04

For information about supported OS versions, see Operating System Support Matrix (MapR 6.x).

Java Version Upgrade All upgrades to core 6.2.0 require upgrading the Java version to JDK 11. The Installer upgrades the Java version if it detects that an upgrade is needed. For more information about Java requirements, see the JDK Support Matrix.