Upgrading CDH4 in a Cloudera Manager Deployment
As of Cloudera Manager 4.5, you can upgrade to CDH4.1.3 (or later) within the Cloudera Manager Admin Console, using parcels and an upgrade wizard. This vastly simplifies the upgrade process. In addition, using parcels enables Cloudera Manager to automate the deployment and rollback of CDH versions. Electing to upgrade using packages means that future upgrades and rollbacks will still need to be done manually.
Before You Begin
- Before upgrading, be sure to read about the latest Incompatible Changes and Known Issues and Workarounds in the CDH4 Release Notes.
- If you are upgrading a cluster that is part of a production system, be sure to plan ahead. As with any operational work, be sure to reserve a maintenance window with enough extra time allotted in case of complications. The Hadoop upgrade process is well understood, but it is best to be cautious. 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 lots of 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.
- Impala - If you have CDH4.1.x with a beta version of Cloudera Impala installed, and you plan to upgrade to CDH4.2 or later, you must also upgrade Impala from the beta version to version 1.0 or later. With a parcel installation you can download and activate both parcels before you proceed to restart the cluster. You will need to change the remote parcel repo URL to point to the location of the released product as described in upgrade procedures referenced below.
- HBase - In CDH4.1.x, an HBase table could have an owner that had full administrative permissions on the table. The owner construct was removed as of CDH4.2.0, and the code now relies exclusively on entries in the ACL table. Since table owners do not have an entry in this table, their permissions are removed on upgrade from CDH4.1.x to CDH4.2.0 or later. If you are upgrading from CDH4.1.x to CDH4.2 or later, and using HBase, you must add permissions for HBase owner users to the HBase ACL table before you perform the upgrade. See the Known Issues in the CDH4 Release Notes, specifically the item "Must explicitly add permissions for owner users before upgrading from 4.1.x" in the Known Issues in Apache HBase section.
- Hive - Hive has undergone major version changes from CDH 4.0 to 4.1 and between CDH 4.1 and 4.2. (CDH 4.0 had Hive 0.8.0, CDH 4.1 used Hive 0.9.0, and 4.2 or later has 0.10.0). This requires you to manually back up and upgrade the Hive metastore database when upgrading between major Hive versions. If you are upgrading from a version of CDH 4 prior to CDH 4.2 to a newer CDH 4 version, you must follow the steps for upgrading the metastore included in the upgrade procedures referenced below.
- Parcels - If you are running Cloudera Manager 4.5 or later, and want to upgrade to CDH4.1.3 or later, see Upgrading CDH4 Using Parcels for instructions. If you have a Cloudera Enterprise license, are performing an upgrade between CDH4 versions, and have enabled HDFS High Availability, you may optionally follow the rolling upgrade procedure.
- Packages - If you want to upgrade to a version of CDH4 earlier than 4.1.2, you must follow the package upgrade instructions (see Upgrading CDH4 Using Packages).
|<< Using Parcels||Upgrading CDH4 Using Parcels >>|