This is the documentation for Cloudera Manager 5.1.x. Documentation for other versions is available at Cloudera Documentation.
Upgrading CDH 5
Use the instructions in this section to upgrade from an earlier version of CDH 5 to the latest version.
If you have a Cloudera Enterprise license and are running HDFS high availability, you can perform a rolling upgrade that lets you avoid cluster downtime.
To upgrade from CDH 4 to CDH 5, use the instructions under Upgrading to CDH 5.
Before You Begin
- Read the CDH 5 Release Notes.
- Read the Cloudera Manager 5 Release Notes.
- Make sure there are no Oozie workflows in RUNNING or SUSPENDED status; otherwise the Oozie database upgrade will fail and you will have to reinstall CDH 4 to complete or kill those running workflows.
- Run the Host Inspector and fix every issue.
- If using security, run the Security Inspector.
- Run hdfs fsck / and hdfs dfsadmin -report and fix any issues.
- Run hbase hbck to make sure there are no inconsistencies.
- Review the upgrade procedure and reserve a maintenance window with enough time allotted to perform all steps. For production clusters, Cloudera recommends allocating up to a full day maintenance window to perform the upgrade, depending on the number of hosts, the amount of experience you have with Hadoop and Linux, and the particular hardware you are using.
- To avoid generating many alerts during the upgrade process, you can enable maintenance mode on your cluster before you start the upgrade. Be sure to exit maintenance mode when you have finished the upgrade, in order to re-enable Cloudera Manager alerts.
| << Performing a Rolling Upgrade on a Cluster | Upgrading CDH 5 Using Parcels >> | |