Considerations for Upgrades Using the Installer
If you use the Installer to upgrade the cluster, some post-upgrade steps for core do not need to be performed. This page describes the post-upgrade steps that are performed by the Installer and the steps that you must perform manually.
This information is relevant to the workflow for Installer upgrades. The information on this page also applies to upgrades performed using Installer Stanzas.
| Post-Upgrade Step for Core | Performed by Installer? | Notes |
|---|---|---|
| Step 1: Restart and Check Cluster Services | Yes, with exceptions. See the notes. | Usually, you do not need to perform this step. When you use the Installer to upgrade, the Installer runs
configure.sh on each node, starts ZooKeeper and Warden, and sets the
new cluster version. If the env_override.sh file is present, the Installer uses environment
variables from the env_override.sh file. If you use the Installer to upgrade, you need to perform this step manually only if you make significant changes to configuration files after the upgrade (see Step 2: Manually Update Configuration Files). |
| Step 2: Manually Update Configuration Files | No | You might need to perform this step. The Installer uses default configuration-file settings and does NOT update configuration files. You must perform this step after upgrading using the Installer only if you have made configuration-file customizations that you want to migrate to the upgraded cluster. Depending on the customization, you might also need to restart services or even the full cluster after updating configuration files. |
| Step 3: Upgrade Clients | No | You need to perform this step. Enabling some new features, such as
mfs.feature.name.container.size.control can cause client failures if
the features are enabled before the clients are upgraded. |
| Step 4: Enable New Features | Yes | You do not need to perform this step. The Installer enables new features as part of a version upgrade. |