Master Upgrade from 3.3.6.x-x to 3.3.6.2-1
Overview
The current ODP release 3.3.6.2-1 supports both the rolling and express upgrade from 3.3.6.x-x, as the stack and services are already on Python3 distribution and running on a JDK11 environment.
Currently supported upgrade types are:
- Rolling Upgrade
- Express Upgrade
Prerequisites
Ensure the following prerequisites are met before upgrading to the latest Ambari or ODP versions.
Remove Custom Mpacks Before Ambari Upgrade
Before upgrading Ambari, it is essential to remove all custom management packs (mpacks) from the system. Keeping them during the upgrade process can lead to stack-related issues, as they are not compatible with our designated stack configuration. Before starting the Ambari ODP healthy functioning as expected
Back Up and Remove Kafka Add-On Services Before Upgrade
Before starting an Express or Rolling upgrade, back up the configurations for Kafka add-on services (Cruise Control, Kafka Connect, and MirrorMaker). After backing up, remove these services to avoid inconsistencies during the upgrade.
When the upgrade is complete, re-add the Kafka add-on services to the cluster using the saved configurations to restore normal operation.
Increase the NameNode Timeout Value
To ensure that Ambari requests to start the NameNode and does not timeout during an upgrade, you must configure the Ambari NameNode restart timeout parameter using upgrade.parameter.nn-restart.timeout in the /etc/ambari-server/conf/ambari.properties file on the Ambari Server host.
You may need to add the restart timeout parameter and value to the Ambari server host following a default installation. For a large cluster, you must add 50% to the usual time (in seconds) that is required to restart the NameNode.
For example, on the Ambari server, observe the time (in seconds) required to restart the active NameNode. If the time taken to restart the active NameNode is more than 10 minutes (600 seconds) and the cluster is large, then add the following parameter to the /etc/ambari-server/conf/ambari.properties file on the Ambari Server host.
parameter.upgrade.parameter.nn-restart.timeout=900parameter.upgrade.parameter.nn-restart.timeout=900After adding or resetting the Ambari NameNode restart parameter, restart the Ambari server before upgrading it to a newer version using the below command.
ambari-server restartDetailed Documentation
Follow the steps below for ODP Master Upgrade.