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

Upgrading Cloudera Manager

You can upgrade an existing Cloudera Manager to the latest version of Cloudera Manager. Upgrading 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 nothing is removed.

As of Cloudera Manager 4.6, the former Cloudera Manager Free Edition is now known as Cloudera Standard, and includes a number of features that were previously available only with Cloudera Manager Enterprise Edition. Specifically, service and activity monitoring features are now available, and require databases to be set up for their use. Thus, upon upgrading to Cloudera Manager 4.6, you will be asked for database information for these services. (You will have the option to use the embedded PostGreSQL database for this).

Understanding Upgrades

The process for upgrading to Cloudera Manager varies based on the starting point. The categories of tasks to be completed include the following:

  • Install any databases that are newly required for this release. (If you are upgrading a Free Edition installation, you are asked to configure databases for the monitoring features that are now part of Cloudera Standard).
  • Upgrade the Cloudera Manager server.
  • Upgrade the hosts in the cluster.

Before Upgrading

  • The Cloudera Manager Server must have SSH access to the cluster hosts and you must log in using a root account or an account that has password-less sudo permission. See Requirements for Cloudera Manager for more information.
  • Ensure there are no running commands. Use the Admin Console's main navigation bar to check for any running commands. You can either wait for commands to complete or abort any running commands. For more information on viewing and aborting running commands, see Viewing Running and Recent Commands.
  • Ensure you have completed any required process for preparing databases, as described in Database Considerations for Cloudera Manager Upgrades.

During the Upgrade

During the upgrade process, the following changes occur:

  • The database schemas are modified for any databases storing information for Cloudera Manager Server, Activity Monitor, Service Monitor, Report Manager, and Host Monitor.
  • Configuration information is reorganized.

After Upgrading

After completing an upgrade to the latest Cloudera Manager (4.6 or later), the following is true:

  • You have re-deployed client configurations to ensure client services have the most current configuration.
  • Required databases are established to store information for Cloudera Manager Server, Hive Metastore, Activity Monitor, Service Monitor, Report Manager, and Host Monitor.
  • The database schemas reflect the current version.
  • The Host Monitor service is added and active.
  • The Cloudera Manager Server and all supporting services, such as the Activity Monitor, Service Monitor, Report Manager, and Host Monitor are updated.

Upgrade Paths

In some cases, completing an upgrade requires changes to your environment, and in other cases, elements are already in place. For example, if you are upgrading your environment from 3.7 to 4.5 or later, you must add Host Monitor, but if you are upgrading from 4.0 beta or 4.0 GA to 4.6, this is not required, as Host Monitor is included in 4.0. The specific steps required vary based on the path taken.

To upgrade from a version older than Cloudera Manager 3.7, begin by upgrading toCloudera Manager 3.7, and then proceed to upgrade from there.

  Warning:

Cloudera Manager 4.5 or later works with CDH3 and CDH4, but does not work with CDH4.0 beta. You must upgrade any installations of CDH4.0 beta.

Begin the upgrade process by evaluating Database Considerations for Cloudera Manager Upgrades.

Upgrading CDH

Cloudera Manager 4 can manage both CDH3 and CDH4, so upgrading existing CDH3 or CDH4 installations is not required. However, to get the benefits of the most current CDH4 features, you may want to upgrade CDH. See the following topics for more information on upgrading CDH:

  Important: Cloudera Manager version 3.x and CDH3 have reached End of Maintenance (EOM) as of June 20, 2013. Cloudera will not support or provide patches for any of the Cloudera Manager version 3.x and CDH3 releases. Even though Cloudera Manager 4.x will continue to support CDH3, it is strongly recommended that you upgrade to CDH4. See Upgrading existing installations of CDH3 to CDH4 for more details.