Apache Ambari Upgrade
Also available as:
PDF

Preparing to Upgrade Ambari

  • Be sure to review the Ambari 2.6.2.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.

  • IF your cluster is SSO-enabled, do not stop Knox before upgrading Ambari.

  • If you are upgrading to Ambari-2.6.x from a version older than Ambari-2.5.2, you must add kerberos.operation.verify.kdc.trust in ambari.properties.

    IF you are using SSL, set the value of kerberos.operation.verify.kdc.trust to true.

    IF you are NOT using SSL, set the value of kerberos.operation.verify.kdc.trust to false.

    Failing to add this property before upgrading, causes the following error when attempting to install any component, post-upgrade:

    Failed to connect to KDC - Failed to communicate with the Active Directory at ldaps:
    //my.ldap.com:636: simple bind failed: my.ldap.com:636 
    Make sure the server's SSL certificate or CA certificates have been imported into Ambari's truststore. 
    Please enter admin principal and password.

The following table lists recommended (), and unsupported (X) upgrade paths.

From / To

2.5.x2.6.x

2.0.x

X

2.1.x

X

2.2.x

X

2.4.x

2.5.x

NA

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

Upgrade Ambari

More Information

Upgrade Ambari Metrics

Add Grafana

Upgrade SmartSense

Ambari 2.6.2.0 Release Notes

Upgrade the Ambari Server version to 2.2