Workflow: Manual Rolling Upgrade
This page summarizes the steps for upgrading from MapR 5.2.x to MapR 6.1.x by using a manual rolling upgrade. In this workflow, the cluster to be upgraded is ; after the upgrade, the cluster will continue to be .
Manual Rolling Upgrade Summary
In a manual rolling upgrade, you upgrade the software one node at a time so that the
cluster as a whole remains operational throughout the process. The manual rolling upgrade
requires you to:
- Perform pre-upgrade checks.
- Perform a rolling upgrade of core.
- Verify that all use cases are functional on the cluster.
- Upgrade the EEP to 6.0.0.
- Merge custom configuration settings.
- Enable MapR 6.1.x features.
- Perform post-upgrade checks.
The workflow later in this section provides more detail to help you get started with a manual rolling upgrade.
Considerations for Manual Rolling Upgrades
Before performing a manual rolling upgrade, note these considerations:
- Rolling upgrades only upgrade core packages, not ecosystem components. A rolling upgrade of ecosystem components is not supported.
- If you choose to do a rolling upgrade on a cluster with core and ecosystem components, the ecosystem components will continue to work during the rolling upgrade as long as the ecosystem components are not updated. If you choose to upgrade core and ecosystem components together, the ecosystem components might not function properly during the upgrade process.
- You can only perform a manual rolling upgrade from the following MapR
versions:
- MapR 5.2.x with EEP 3.0.1 or later
- MapR 6.0.0 with EEP 4.0.x or 4.1.x
- MapR 6.0.1 with EEP 5.0.x
- MapR 6.1.0 with EEP 6.x.x
- If your cluster is running MapR 5.2.x but your EEP is not 3.0.1 or later (for example, you have EEP 2.0.3), you must upgrade to EEP 3.0.1 or later before you can do a rolling upgrade to MapR 6.1.x. See Upgrading Ezmeral Ecosystem Packs.
- If you want to use a manual rolling upgrade from a pre-5.2 release to MapR 6.1.x, you must do multiple rolling upgrades, one of which upgrades your cluster to a MapR / EEP combination that can upgrade directly to MapR 6.1.x.
- After upgrading MapR Core to MapR 6.1.x, you must upgrade ecosystem components to EEP 6.0.0 or later, and this must be done before you enable MapR 6.1.x features.
Manual Rolling Upgrade Workflow
High-Level Steps | Detailed Information (review all items unless noted otherwise) |
---|---|
1. Understand MapR Core/MEP Dependencies | |
2. Plan for the MapR Core Upgrade | |
3. Plan for the EEP Upgrade | |
4. Perform Pre-Upgrade Steps for MapR Core | |
5. Prepare to Upgrade EEP Components | |
6. Set up Repositories | |
7. Perform the Manual Rolling Upgrade | |
8. Upgrade the EEP Components | |
9. Perform Post-Upgrade Steps for EEP | |
10. Perform Post-Upgrade Steps for MapR Core | |
11. Install Additional MapR Core Features |
NOTE This page includes the steps to generate Object Store certificates by using
manageSSLKeys.sh . The certificates must be generated after
upgrading and running configure.sh -R . If you fail to generate
the certificates, you will not be able to use the Object
Store. |
12. Secure the Upgraded Cluster |