Upgrading Cloudera Manager

Minimum Required Role: Cluster Administrator (also provided by Full Administrator) This feature is not available when using Cloudera Manager to manage Data Hub clusters.

This topic describes how to upgrade Cloudera Manager from any 5.x or 6.x version to a higher version of Cloudera Manager 5.x, 6.x, or 7.1 and higher, including major, minor, and maintenance releases. The upgrade procedures use operating system command-line package commands to upgrade Cloudera Manager, and then complete the upgrade using Cloudera Manager.

When you upgrade Cloudera Manager, you use RPM-based package commands to upgrade the software on the Cloudera Manager server host and then Cloudera Manager manages upgrading the Cloudera Manager Agents on the remaining managed hosts. Cloudera Manager can also automatically install some versions of the required JDK on the managed hosts. For CDH clusters, Cloudera Navigator is also upgraded when you upgrade Cloudera Manager.

Upgrades are not supported between all versions of Cloudera Manager, CDH, or Cloudera Runtime. See Supported Upgrade Paths

Cloudera Navigator is also upgraded when you upgrade Cloudera Manager 5.x or 6.x. Cloudera Navigator has been replaced by Apache Atlas as of Cloudera Runtime 7.0.3. If you are using Cloudera Manager 7.0.3 or higher to manage CDH clusters, those clusters can continue using Cloudera Navigator.

The Cloudera Manager upgrade process does the following:
  • Upgrades the database schema to reflect the current version.
  • Upgrades the Cloudera Manager Server and all supporting services.
  • Upgrades the Cloudera Manager agents on all hosts.
  • Redeploys client configurations to ensure that client services have the most current configuration.
  • Upgrades Cloudera Navigator (for upgrades to Cloudera Manager 7.1, you can transition Cloudera Navigator to Apache Atlas).
To upgrade Cloudera Manager, you perform the following tasks:
  1. Back up the Cloudera Manager server databases, working directories, and several other entities. These backups can be used to restore your Cloudera Manager deployment if there are problems during the upgrade.
  2. Upgrade the Cloudera Manager server software on the Cloudera Manager host using package commands from the command line (for example, yum on RHEL systems). Cloudera Manager automates much of this process and is recommend for upgrading and managing your CDH clusters.
  3. Upgrade the Cloudera Manager agent software on all cluster hosts. The Cloudera Manager upgrade wizard can upgrade the agent software (and, optionally, the JDK), or you can install the agent and JDK software manually. The CDH software is not upgraded during this process.

If you are upgrading from Cloudera Manager 5.x to a higher version of Cloudera Manager 5.x, you can also upgrade Cloudera Manager using tarballs. See Upgrading Cloudera Manager 5 Using Tarballs for procedures to upgrade to the latest version of Cloudera Manager 5.x. (Click Other Versions to locate the document for earlier versions.)

Upgrading Cloudera Manager does not upgrade CDH/Cloudera Runtime clusters. See Upgrading a Cluster for upgrade procedures.

Overview of Upgrading Cloudera Navigator Components

Cloudera Navigator Metadata and Audit servers are automatically upgraded when you upgrade Cloudera Manager. You can also optionally upgrade other Cloudera Navigator components such as Cloudera Navigator Key Trustee Server, Cloudera Navigator Key HSM, and Cloudera Navigator Encrypt. You do not have to upgrade these components along with Cloudera Manager or CDH upgrades. For compatibility information, see: Product Compatibility Matrix for Cloudera Navigator Encryption (Cloudera Manager 6.x) or Product Compatibility Matrix for Cloudera Navigator Encryption (Cloudera Manager 5.x).

See Upgrading Cloudera Navigator Data Encryption.