Workflow: Manual Rolling Upgrade from Release 6.1.x to 6.2
This page summarizes the steps for upgrading from release 6.1.x to release 6.2 by using a manual rolling upgrade. 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 manual steps.
NOTE This workflow assumes that the cluster to be upgraded is running release
6.1.x with EEP 6.3.1 (or later EEP 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
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 7.x.
- Merge custom configuration settings.
- Enable release 6.2.0 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.
- After upgrading core to release 6.2.0, you must upgrade ecosystem components to EEP 7.0.0 or later, and this must be done before you enable release 6.2.0 features.
Manual Rolling Upgrade Workflow
High-Level Steps | Detailed Information (review all items unless noted otherwise) |
---|---|
1. Understand Core/MEP Dependencies | |
2. Plan for the Core Upgrade | |
3. Plan for the EEP Upgrade | |
4. Perform Pre-Upgrade Steps for 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 Core | |
11. Install Additional 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 |