Installation and Upgrade Notes (Release 6.2.0)

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

If you are upgrading from release 5.x or 6.x, be sure to review the following notes first:

Installing Release 6.2.0 (Any Method)

Note these considerations for new installations of release 6.2.0, which apply regardless of the method you use to install the release:
Ubuntu 16.04 Installations Require Manual Installation of JDK Before Using Installer Before using Installer 1.14 on Ubuntu 16.04 nodes, you must manually install the JDK. If you are using Installer 1.14 on RHEL/CentOS, the Installer installs OpenJDK 11 for you. For more information, see the Installer Prerequisites and Guidelines.
SUSE Support HPE Ezmeral Data Fabric release 6.2.0 currently is not supported on SUSE Linux.
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 theses 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 the server configure.sh command is run 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 the data-fabric 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:
KMIP Installation Is Not Supported Using the Installer Installer 1.14 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 (Any Method)

Upgrades to release 6.2.0 are currently not supported. This includes manual upgrades and upgrades using the Installer or Installer Stanzas. The upgrade process will be verified and made available shortly.