Preparing to Upgrade
Be sure to review the Ambari 2.6.1.0 release notes for Known Issues and Behavioral Changes.
You must have root, administrative, or root-equivalent authorization on the Ambari server host and all servers in the cluster.
You must backup the Ambari Server database.
You must make a safe copy of the Ambari Server configuration file found at
/etc/ambari-server/conf/ambari.properties.Plan to upgrade the Ambari Metrics service:
Record the location of the Metrics Collector component before you begin the upgrade process.
You must stop the Ambari Metrics service from Ambari Web.
After upgrading Ambari, you must also upgrade Ambari Metrics System and add the Grafana component.
After upgrading Ambari, you must also upgrade SmartSense.
Upgrade Ambari to version 2.5x or 2.6x, based on your current Ambari Server version.
The following table lists recommended (
), and unsupported (X) upgrade paths.
|
From / To | 2.5.x | 2.6.x |
|---|---|---|
|
2.4.0.x |
|
|
| 2.4.2.x | N/A | |
|
2.5.x | N/A | |
During Ambari upgrade, the existing
/var/lib/ambari-server/ambari-env.sh file 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.
Next Steps
More Information