Upgrade Ambari
Prerequisite
Ensure the following prerequisite is met to upgrade to the latest Ambari.
Prior to 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.
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=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 restartRefer to the following documentations and follow the steps in the specified order: