Workflow: Installer Upgrade from Release 6.1 to 6.2

This page summarizes the steps for upgrading from core 6.1 to 6.2 by using the Installer.

Note: This workflow assumes that the cluster to be upgraded is running release 6.1.0 with MEP 6.3.1 (or later MEP 6.3.x), and the cluster operating system is one of the following:

RHEL / CentOS 8.3
RHEL / CentOS 8.2
Ubuntu 18.04
Ubuntu 16.04

In this workflow, the cluster to be upgraded is nonsecure; after the upgrade, the cluster will continue to be nonsecure, but can be secured by using the Incremental Install function of the Installer.

MapR Installer Upgrade Summary

In an upgrade using the Installer, the Installer shuts down core on the entire cluster, upgrades and configures core, starts core, upgrades MEP components, and then starts the MEP components. Like the offline manual upgrade, the Installer upgrade is an offline upgrade. The Installer upgrade requires you to:

Plan for the upgrade.
Update the Installer to version 1.14 or later.
Launch the Installer and select Version Upgrade.
Complete the upgrade through the Installer.
Merge custom configuration settings.
Perform post-upgrade checks.

The workflow later on this page provides more detail to help you get started with the Installer upgrade.

Considerations for Installer Upgrades

Before upgrading using the Installer, note these considerations:

Upgrades using the Installer are supported only from release 5.2.x with MEP 3.0.1 or later.
If security is enabled on the cluster – either data-fabric default security or custom security – you cannot upgrade from release 5.2.x using the Installer; you must use one of the manual upgrade workflows. Note that upgrades from secure release 6.0.0 or 6.0.1 clusters can be done using the Installer, as described in Planning Your Core Upgrade.
Security settings cannot be changed during a version upgrade using the Installer.
Before upgrading using the Installer, you must update the installer to version 1.14 or later.
This procedure assumes that the cluster was originally installed using the Installer or an Installer Stanza. If the cluster was installed manually, you must use the manual steps to upgrade or use probe and import to generate the installer database.
When upgrading to release 6.2 using the Installer, MEP 4.x or later is upgraded automatically to MEP 7.0.0.

Installer Upgrade Workflow

High-Level Steps	Detailed Information (review all items unless noted otherwise)
1. Understand Core/MEP Dependencies	Operating System Support Matrix (Release 6.x) MEP Support and Lifecycle Status Component Versions for Released MEPs
2. Plan for the Core Upgrade	Installation and Upgrade Notes (Release 6.2.0) Planning Your Core Upgrade
3. Plan for the MEP Upgrade	Planning Ecosystem Pack (MEP) Upgrades
4. Perform Pre-Upgrade Steps for Core	Preparing to Upgrade Core
5. Prepare to Upgrade MEP Components	Preparing to Upgrade the Ecosystem Pack
6. Upgrade the Installer to Version 1.14 or later	Checking the Installer Version Updating the Installer Using the Installer
7. Upgrade the OS	When Upgrading Core with the Installer Requires an OS Upgrade
8. Select the Version Upgrade Option	Upgrading Core With the Installer
9. Complete the Upgrade Through the Installer	Online Help for Installer Fields
10. Perform Post-Upgrade Steps forCore	Considerations for Upgrades Using the Installer Step 2: Manually Update Configuration Files Step 3: Upgrade Clients
11. Perform Post-Upgrade Steps for MEP	Finishing the Ecosystem Pack Upgrade
12. Secure the Upgraded Cluster	Securing the Upgraded Cluster