Installation and Upgrade Notes (MapR 6.0.1)
This page describes considerations for upgrading to Map 6.0.1.
If you are upgrading from MapR 4.x or 5.x, be sure to review Installation and Upgrade Notes (MapR 6.0.0) first.
Upgrading to MapR 6.0.1 Using the MapR Installer
Note these considerations for upgrading to MapR 6.0.1 using the MapR Installer:
MapR Installer 1.9.0 | Before upgrading, update the MapR Installer to version 1.9.0 or later. Only MapR Installer 1.9.0 or later can be used with MapR 6.0.1 and MEP 5.0.0. |
MapR 6.0.1 and MEP 5.0.0 | MapR 6.0.1 requires MEP 5.0.0. MEP 4.x can coexist with MapR 6.0.1 only temporarily in the context of an upgrade. |
Version Upgrade | Upgrading to MapR 6.0.1 using the MapR Installer requires you to perform a version upgrade. Even if the cluster to be upgraded is running MapR 6.0.0, you cannot complete the upgrade by doing a maintenance update. A maintenance update assumes that the MEP version will not change, but upgrading from MapR 6.0.0 to MapR 6.0.1 requires upgrading the MEP version from 4.x to 5.0.0 or later. |
Changes to Auto-Provisioning Templates | MapR 6.0.1 introduces new and changed auto-provisioning templates. See the Installer 1.9 information in Auto-Provisioning Templates. |
Renamed Services | The following services are renamed in MapR Installer 1.9.0: Old Name → New Name OJAI Query Service → OJAI Distributed Query Service HBase/MapR-DB Common → MapR DataBase |
Enhanced Security for Passwords | To support enhanced security, the MapR Installer:
|
MapR DataBase Service and Gateways | Installing the MapR DataBase service automatically triggers installation of the gateway package, the MapR Data Access Gateway, and some streams components, depending on the auto-provisioning template you choose. |
Querying Using Secondary Indexes | New options are available for configuring the cluster to query secondary indexes. See Preparing Clusters for Querying using Secondary Indexes on JSON Tables. |
Regenerating the mapruserticket File |
If you applied
mapr-patch-6.0.1.20180404222005.GA-20180710151556 or later, changes
to the CanImpersonate parameter of the
mapruserticket file 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 the patch, all mapruserticket files were generated
with CanImpersonate = false . The patch enforces 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. |
Upgrading to MapR 6.0.1 Manually
Note these considerations for upgrading to MapR 6.0.1 using manual steps:
MapR 6.0.1 and MEP 5.0.0 | MapR 6.0.1 requires MEP 5.0.0. MEP 4.x can coexist with MapR 6.0.1 only temporarily in the context of an upgrade. |
Querying Using Secondary Indexes | New options are available for configuring the cluster to query secondary indexes. See Preparing Clusters for Querying using Secondary Indexes on JSON Tables. |
MapR DataBase Service and Gateways | If you install the mapr-hbase-common package, consider
installing these additional packages that are installed automatically when
mapr-hbase-common is installed by the MapR Installer:
|
Installing Metrics and Logging Components | The manual steps for installing MapR Monitoring metrics and logging components now include steps for specifying passwords for Grafana and Elasticsearch: |