This is the documentation for Cloudera Manager 5.0.x. Documentation for other versions is available at Cloudera Documentation.

Upgrading Cloudera Manager

Upgrading Cloudera Manager preserves existing data and settings, while enabling the use of the new features provided with the latest product versions. To enable new features, some new settings are added, and some additional steps may be required, but no existing configuration is removed.
  Note: When an upgraded Cloudera Manager adds support for a new feature (for example, Sqoop 2, WebHCat, and so on), it does not install the software on which the new feature depends. If you install CDH and managed services from packages, you must add the packages to your managed hosts first, before adding a service or role that supports the new feature.

Understanding Upgrades

The process for upgrading Cloudera Manager varies depending on the starting point. The categories of tasks to be completed include the following:
  • Install any databases required for the release. In Cloudera Manager 5, the Host Monitor and Service Monitor roles use an internal database that provides greater capacity and flexibility for current and future uses. You no longer need to configure an external database for this purpose. If you are upgrading from Cloudera Manager 4, this transition is handled automatically. If you are upgrading a Free Edition installation and you are running a MapReduce service, you are asked to configure an additional database for the Activity Monitor that is part of Cloudera Express.
  • Upgrade the Cloudera Manager Server.
  • Upgrade the Cloudera Manager Agent. This can be done via an upgrade wizard that is invoked when you connect to the Admin Console or by manually installing the Cloudera Manager Agent packages.

Upgrading Cloudera Manager

You can upgrade from any version of Cloudera Manager 4 running CDH 4, to Cloudera Manager 5 or from Cloudera Manager 5 to a later version of Cloudera Manager 5. See the instructions at:
  • Upgrading Cloudera Manager 5 to the Latest Cloudera Manager. After upgrading Cloudera Manager 5, the following is true:
    • Database schema is upgraded to reflect the current version.
    • The Cloudera Manager Server and all supporting services are updated.
    • Client configurations are redeployed to ensure client services have the most current configuration.
  • Upgrading Cloudera Manager 4 to Cloudera Manager 5 and Upgrading Cloudera Manager 3.7.x. After upgrading to Cloudera Manager 5, the following is true:
    • Database schema is upgraded to reflect the current version. Data from the existing Host and Service Monitor databases is migrated.
    • The Cloudera Manager Server and all supporting services are updated.
    • Client configurations are redeployed to ensure client services have the most current configuration.
    • Cloudera Manager 5 continues to support a CDH 4 cluster with an existing High Availability deployment using NFS shared edits directories. However, if you disable High Availability in Cloudera Manager 5, you will only be able to re-enable High Availability using Quorum-based Storage. CDH 5 does not support enabling NFS shared edits directories with High Availability.

Upgrading CDH

Cloudera Manager 5 can manage both CDH 4 and CDH 5, so upgrading existing CDH 4 installations is not required. However, to get the benefits of the most current CDH features, you may want to upgrade CDH. See the following topics for more information on upgrading CDH:
  • Upgrading CDH 4 - Follow this path to upgrade existing installations of CDH 4 to the latest version of CDH 4.
  • Upgrading to CDH 5 - Follow this path to upgrade existing installations of CDH 4 to CDH 5.

Continue reading:

Page generated September 3, 2015.