Be sure to review the Release Notes for this Ambari release 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.If you are using Ambari with JDK 1.6, you must first move to JDK 1.7 before attempting to upgrade to Ambari 2.1. Refer the the Ambari Reference Guide for the Ambari version you are currently running for instructions on Changing the JDK.
If you are managing Ganglia and Nagios from Ambari:
Support for managing Ganglia and Nagios from Ambari has been removed.
Record the location of the Nagios server before you begin the upgrade process.
Record the location of the Ganglia server before you begin the upgrade process.
You must stop the Nagios and Ganglia services from Ambari Web.
After upgrading Ambari, you must remove Nagios and Ganglia from your cluster and replace with Ambari Alerts and Metrics. For more information, see Migrate to Ambari Alerts and Metrics in Ambari.
If you are on Ambari 1.7 or earlier:
If your cluster has Kerberos enabled, you must review Adjusting for Kerberos and perform the pre- and post-upgrade steps required.
If you are on Ambari 2.0, or later:
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 service.
Proceed to Upgrade to Ambari 2.1.
![[Note]](../common/images/admon/note.png) | Note |
|---|---|
If your current Ambari version is 1.4.1 or below, you must upgrade the Ambari Server version to 1.7 before upgrading to version 2.1. |
| Note |
|---|---|
During Ambari upgrade, the existing
|
