When preparing to upgrade Ambari and the HDP Cluster, we strongly recommend you review this checklist of items to confirm your cluster operation is healthy. Attempting to upgrade a cluster that is operating in an unhealthy state can produce unexpected results.
![[Important]](../common/images/admon/important.png) | Important |
|---|---|
If planning to upgrade Ambari and upgrade to a new HDP minor version (for example: moving from HDP 2.1 to HDP 2.2), upgrade Ambari to the lastest version before upgrading the cluster. Refer to the Stack Compatibility Matrix to see which HDP versions each Ambari version supports. |
Ensure all services in the cluster are running.
Run each Service Check (found under the Service Actions menu) and confirm they execute successfully.
Clear all alerts, or understand why they are being generated. Remediate as necessary.
Confirm start and stop for all services are executing successfully.
Time service start and stops. The time to start and stop services is a big contributor to overall upgrade time so having this information handy is useful.
Download the software packages prior to the upgrade. Place them in a local repository and/or consider using a storage proxy since multi-gigabyte downloads will be required on all nodes in the cluster. Refer to Using a Local Repository for more information.
Ensure point-in-time backups are taken of all DBs supporting the clusters. This includes (among others) Ambari, Hive Metastore, Ranger and Oozie.
For Ambari Upgrades
This (Ambari 2.0.2) Upgrade Guide will help you upgrade your existing Ambari install to version 2.0. If you are upgrading to another Ambari version, please be sure to use the Ambari Upgrade Guide for that version.
Be sure to review the Known Issues and Behavioral Changes for this Ambari release in the Ambari 2.0.2 Release Notes.
For HDP Cluster Upgrades
Ensure sufficient disk space on
/usr/hdp/<version>(roughly 3GB for each additional HDP release).New service user accounts and groups may be required/created during the upgrade. This includes service accounts such as ams, flume, and kafka. Any operational procedures required to support these new service accounts should be performed prior to the upgrade. The accounts will typically be required on all nodes in the cluster.
If your cluster includes Storm, document any running Storm topologies.
