Apache Ambari Upgrade
Also available as:
PDF

Prerequisites

To perform an HDP upgrade using Ambari, your cluster must meet the following prerequisites, whether you intend to perform a Rolling or Express upgrade. Meeting these prerequisites is essential for Ambari to know the cluster is in a healthy operating mode and can successfully manage the upgrade process. Your cluster must meet additional prerequisites for a Rolling Upgrade, which ensure that the cluster is configured properly to support the rolling upgrade orchestration process.

HDP Version

All hosts must have the target HDP version installed.

Disk Space

Be sure to have adequate space on /usr/hdp for the target HDP version. Each complete install of an HDP version will occupy about 2.5 GB of disk space.

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:

  • Any hosts in Maintenance Mode must not be hosting any Service Master Components.

  • Any host in Maintenance Mode that is not hosting Master Components is allowed but you will receive a warning. You can proceed with your upgrade but these hosts will not be upgraded and before you can finalize the upgrade, you must delete the hosts from the cluster.

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 you are upgrading to HDP 2.5 and have Atlas installed in your HDP 2.3 or 2.4 cluster, Atlas must be removed prior to upgrading to HDP 2.5 after you have upgraded to Ambari-2.4.x.

Do NOT remove Atlas service via REST API.

Use the Remove Service capability to completely remove Atlas from your cluster and then perform your cluster upgrade to HDP 2.5 and re-add Atlas service to your cluster.

[Note]Note

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.5 with the new version of Atlas.

Kerberos - Kafka

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.

Ranger Policy Export/Import DB Requirements

HDP-2.6 and higher versions include Ranger policy import/export. The minimum database requirements for this feature are as follows:

  • MariaDB: 10.1.16+

  • MySQL: 5.6.x+

  • Oracle: 11gR2+

  • PostgreSQL: 8.4+

  • MS SQL: 2008 R2+

Apache Zeppelin Notebooks

If you are upgrading to HDP-2.6.3:

  • HDFS is now used for notebook storage, so you should copy your existing custom notebooks to the /user/zeppelin/notebook folder in HDFS (you may need to create this HDFS folder).

  • The interpreter.json configuration file has been moved from local storage to HDFS. If you have customized your interpreter.json file, you should copy this file to the /user/zeppelin/conf folder in HDFS.

  • The zeppelin.interpreter.config.upgrade property has been added in Zeppelin Notebook > Configs > Advanced zeppelin-config. When set to true (the default value), the default interpreter parameters are reset whenever Zeppelin is restarted. To disable this feature, set this property value to false.

  • Even though Zeppelin uses HDFS storage, the notebook directory under zeppelin-server (/usr/hdp/current/zeppelin-server/notebook) must exist – otherwise Zeppelin will not restart.

More Information

Rolling Upgrade Prerequisites

Register and Install Target Version

Remove Service