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)
Hadoop and YARN Are Provided as Ecosystem Components | Beginning with core 6.2.0 and EEP
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 EEP repository. This permits 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. |
SLES Support | HPE Ezmeral Data Fabric 6.2.0 is supported on SLES 15 SP2. For a complete list of supported operating systems, see Operating System Support Matrix |
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:
|
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 Key Store and Trust Store Files. |
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 Understand Software Versions. |
Installing Release 6.2.0 Using the Installer
Enabling Package Repositories for SLES 15 | Before using the Installer for a new data-fabric installation on SLES 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 SLES 15 SP2 (or a later supported service
pack):
If
you are developing applications on the cluster, run the following command on all
nodes:
To
view the available SUSE modules and learn how to enable or disable them, use the
To
add Packagehub to the repositories, use the instructions on this page. For
example:
|
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. |
Installer 1.17.0.0 and Ubuntu |
Installer 1.17.0.0 cannot be used with older versions of Ubuntu. For more information, see Installer Updates and Selecting an Installer Version to Use. |
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)
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 |
|
|
5.2.x or 6.0.x |
|
Upgrade Considerations (All Upgrade Methods)
Core and EEP Requirements for Upgrading | As indicated in the high-level upgrade steps earlier on this page, clusters to be upgraded to release 6.2.0 must be installed with release 6.1.0 or 6.1.1 and EEP 6.3.1 (or later EEP 6.3.x) before upgrading. If your cluster is on release 5.2.x or 6.0.x, you must first upgrade to release 6.1.x and EEP 6.3.1 (or later EEP 6.3.x). |
Upgrades to RHEL / CentOS 8.1 | Upgrades from RHEL / CentOS 7.x to RHEL / 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 RHEL 8.2, 8.3, or 8.4, or 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:
|
Hadoop and YARN Are Provided as Ecosystem Components | Beginning with core 6.2.0 and EEP 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 EEP 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 EEP 7.0.0 | Release 6.2.0 requires EEP 7.0.0 or later. For more information, see EEP Support and Lifecycle Status. |
Release 6.2.0 and EEP 8.0.0 |
EEP 8.0.0 can be used with core 6.2.0 on Ubuntu 18.04 but is not supported with core 6.2.0 on Ubuntu 16.04. For a list of the operating systems that each EEP can support, see EEP Components and OS Support. For a list of the operating systems that different versions of core can support, see Operating System Support Matrix. Impala and Sentry are not included in EEP 8.0.0 and later. For more information, see Discontinued Ecosystem Components. If Impala or Sentry are installed on your cluster and you plan to upgrade to EEP 8.0.0, you must remove them before upgrading. If you upgrade to EEP 8.0.0 using the Installer, the Installer will remove them as part of the upgrade. |
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- |
Enabling Policy-Based Security (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):
To enable
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 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 EEPs, and only Installer 1.14 or later can be used with data-fabric release 6.2.0 and EEP 7.x.x. For more information, see Selecting an Installer Version to Use. |
Installer 1.17.0.0 |
Installer 1.17.0.0 cannot be used with older versions of Ubuntu. For more information, see Installer Updates and Selecting an Installer Version to Use. |
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:
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. |