Upgrading Cloudera Manager
You can upgrade an existing Cloudera Manager to Cloudera Manager 5. 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 no existing configuration is removed.
The process for upgrading to Cloudera Manager 5 varies depending on the starting point. The categories of tasks to be completed include the following:
- Install any databases that are required for this 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. This transition is handled automatically. You no longer need to configure an external database for this purpose. 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 software. This can be done via an upgrade wizard that is invoked when you connect to the Admin Console.
Before Upgrading to Cloudera Manager 5
- Upgrade Cloudera Manager 3.7.x to Cloudera Manager 4 - See Upgrading Cloudera Manager 3.7.x.
- Upgrade all CDH 3 clusters to CDH 4 - See Upgrading CDH 3.
- Obtain host credentials - You must have SSH access and be able to log in using a root account or an account that has password-less sudo permission. See Cloudera Manager Requirements for more information.
- Stop 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.
- Prepare databases - See Database Considerations for Cloudera Manager Upgrades.
Upgrading Cloudera Manager
You can upgrade from any version of Cloudera Manager 4 running CDH 4, to Cloudera Manager 5. See the instructions at Upgrading Cloudera Manager 4 to Cloudera Manager 5.
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:
After completing an upgrade to Cloudera Manager 5, the following is true:
- Required databases are established to store information for Cloudera Manager Server, Hive Metastore, Activity Monitor (if you are running a MapReduce service), Reports Manager, and optionally Cloudera Navigator. The database schema 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.