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.

Download, Distribute, and Activate the Parcel

1. In the Cloudera Manager Admin Console, click the Parcels indicator in the top navigation bar ( or ).
2. Click Download for the version(s) you want to download. If the parcel you want is not shown here — for example, if you want to upgrade to a version of CDH that is not the most current version — you can add parcel repositories through the Parcel Configuration Settings page. You can find the locations of the previous CDH 5 parcels at http://archive.cloudera.com/cdh5/parcels/. If your Cloudera Manager Server does not have Internet access, you can obtain the required parcel file(s) and put them into a repository. See Creating and Using a Parcel Repository for more details.
3. When the download has completed, click Distribute for the version you downloaded.
4. When the parcel has been distributed and unpacked, the button will change to say Activate.
5. Click Activate. A pop-up that offers to restart your services displays.

Upgrade the Oozie ShareLib

1. Go to the Oozie service.
2. Select Actions > Stop and click Stop to confirm.
3. Select Actions > Install Oozie ShareLib and click Install Oozie ShareLib to confirm.
4. When the command completes, click Close.

Upgrade Spark

Required if you are updating from CDH 5.0 to 5.1.

1. Go to the Spark service.
2. Select Actions > Upload Spark Jar and click Upload Spark Jar to confirm.
3. When the command completes, click Close.
4. Select Actions > Create Spark History Log Dir and click Create Spark History Log Dir to confirm.
5. When the command completes, click Close.

Upgrade Sqoop

1. Go to the Sqoop service.
2. Select Actions > Stop and click Stop to confirm.
3. Select Actions > Upgrade Sqoop and click Upgrade Sqoop to confirm.
4. When the command completes, click Close.

Restart the Services

1. On the Home page, click to the right of the cluster name and select Restart.
2. Click the Restart button in the confirmation pop-up that appears. The Command Details window shows the progress of starting services.

Remove the Previous CDH 5 Version Packages

If your previous installation of CDH was done using packages, you must remove those packages on all hosts on which you installed the parcels and refresh the symlinks so that clients will run the new software versions. Skip this step if you installed the previous version of CDH 5 using parcels.

1. Uninstall the CDH packages on each host:
   • Not including Impala and Search

     Operating System	Command
     RHEL	$ sudo yum remove bigtop-utils bigtop-jsvc bigtop-tomcat hue-common sqoop2-client
     SLES	$ sudo zypper remove bigtop-utils bigtop-jsvc bigtop-tomcat hue-common sqoop2-client
     Ubuntu or Debian	$ sudo apt-get purge bigtop-utils bigtop-jsvc bigtop-tomcat hue-common sqoop2-client

   • Including Impala and Search

     Operating System	Command
     RHEL	$ sudo yum remove 'bigtop-*' hue-common impala-shell solr-server sqoop2-client
     SLES	$ sudo zypper remove 'bigtop-*' hue-common impala-shell solr-server sqoop2-client
     Ubuntu or Debian	$ sudo apt-get purge 'bigtop-*' hue-common impala-shell solr-server sqoop2-client

Deploy the New Client Configuration Files

1. On the Home page, click to the right of the cluster name and select Deploy Client Configuration.
2. Click the Deploy Client Configuration button in the confirmation pop-up that appears.

Update Symlinks for the Newly Installed Components

$ sudo service cloudera-scm-agent restart