Preparing to Upgrade Ambari
Be sure to review the Ambari 220.127.116.11 release notes for Known Issues and Behavioral Changes.
You must have root, administrative, or root-equivalent authorization on the Ambari Server host and all Ambari Agent hosts in the cluster.
You must backup the Ambari Server database.
You must make a safe copy of the Ambari Server configuration file found at
If your cluster is SSO-enabled, do not stop Knox before upgrading Ambari.
The following table lists recommended (), and unsupported (X) upgrade paths.
|From / To||Ambari 2.7.x||Ambari 2.6.x|
During Ambari upgrade, the existing
is overwritten and a backup copy of
ambari-env.sh (with extension
.rpmsave) is created. If you have manually modified
ambari-env.sh (for example, to change Ambari Server heap), you will need to
re-apply your changes to the new file.