Prerequisites
To perform an HDP upgrade using Ambari, your cluster must meet the following prerequisites. These prerequisites are required regardless of Rolling or Express upgrade because these checks are important for Ambari to know the cluster is in a healthy operating mode and can be successfully managed from Ambari. However, there are additional prerequisites for a Rolling Upgrade that require your cluster to be configured a certain way to support the rolling upgrade orchestration process.
Check | Description |
---|---|
HDP Version |
All hosts must have the target HDP version installed. See the Register and Install Target Version section for more information. |
Disk Space |
Be sure to have adequate space on |
Ambari Agent Heartbeats |
All Ambari Agents must be communicating and heartbeating to Ambari Server. Any hosts that are not heartbeating must be in Maintenance Mode. |
Host Maintenance Mode |
The following two scenarios are checked:
|
Service Maintenance Mode |
No Services can be in Maintenance Mode. |
Services Started |
All Services must be started. |
Service Checks |
All Service Checks must pass. Be sure to run Service Actions > Run Service Check on all services (and remediate if necessary) prior to attempting an HDP upgrade. |
Atlas Check |
If Atlas is installed in your HDP 2.3 or 2.4 cluster, we strongly advise upgrading your cluster, as follows:
If you are using Atlas on HDP-2.3 or 2.4; Do Not upgrade to Ambari-2.4.x until you are ready to upgrade to HDP-2.5x (which includes Atlas 0.7x). |
Important | |
---|---|
If your cluster has Kerberos enabled, includes Kafka and you are running HDP 2.2, since Kafka in HDP 2.2 did not support running Kerberized, after upgrade to HDP 2.3 or later (regardless if you perform an Express or Rolling Upgrade), Kafka will then be Kerberos enabled. Plan to adjust your use of Kafka accordingly. Ambari will perform a check to see if your cluster would encounter this issue and warn you prior to performing the HDP upgrade. |