Getting Started Upgrading Cloudera Manager
Before you upgrade Cloudera Manager, you need to gather some information and review the limitations and release notes. Fill in the My Environment form below to customize your Cloudera Manager upgrade procedures. See the Collect Information section below for assistance in locating the required information.
Loading Filters ... 7.1.3 7.1.2 7.1.1 7.0.3 6.3.3 6.3.1 6.3.0 6.2.1 6.2.0 6.1.1 6.1.0 6.0.1 6.0.0 5.16 5.15 5.14 5.13 5.12 5.11 5.10 5.9 5.8 5.7 5.6 5.5 5.4 5.3 5.2 5.1 5.0 6.3.3 6.3.2 6.2.1 6.2.0 6.1.1 6.1.0 6.0.1 6.0.0 5.16 5.15 5.14 5.13 5.12 5.11 5.10 5.9 5.8 5.7 5.6 5.5 5.4 5.3 5.2 5.1 5.0 7.1.3 7.1.2 7.1.1 7.0.3
Review Requirements for upgrades from Cloudera Manager 5 to Cloudera Manager 6
- Log in to the Cloudera Manager Server host.
- Collect the following information about your environment and fill in
the form above. This information will be remembered by your browser on
all pages in this Upgrade Guide.
- The current version of the Operating
... com.cloudera.cmf.db.type=mysql com.cloudera.cmf.db.host=database_hostname:database_port com.cloudera.cmf.db.name=scm com.cloudera.cmf.db.user=scm com.cloudera.cmf.db.password=SOME_PASSWORD
- Log in to the Cloudera Manager Admin console and find the following:
- The version of Cloudera Manager used in your cluster. Go to .
- The version of the JDK deployed in the cluster. Go to .
- The current version of the Operating System:
Preparing to Upgrade Cloudera Manager
- You must have SSH access to the Cloudera Manager server hosts and be able to log in using the root account or an account that has password-less sudo permission for all hosts.
- Review the following when upgrading to Cloudera Manager 5.x:
- Review the following when upgrading to Cloudera Manager 6.x:
- Review the following when upgrading to Cloudera Manager 7.1 or higher:
You may be required to upgrade the operating system before upgrading. See Operating System Requirements to determine operating system support for the version of Cloudera Manager you are upgrading to. Depending on the support, you may need to upgrade the operating system.
If you must or choose to upgrade to a supported operating system, you must determine whether to upgrade the operating system first or Cloudera Manager first. If the both the current version of Cloudera Manager and the version you are upgrading to both support newer version of the operating system but the new version of Cloudera Manager does not support the older operating system, you must upgrade to the newer operating system before upgrading Cloudera Manager. If this is not true, then you must upgrade Cloudera Manager before upgrading the operating system.For example, consider the following upgrade from Cloudera Manager 5.12.1 to Cloudera Manager 5.16.1 and an operating system upgrade from RHEL 7.4 to 7.6:
- Cloudera Manager 5.12.1 supports only RHEL 7.4
- Cloudera Manager 5.16.1 supports RHEL 7.4 and RHEL 7.6
- Install a supported version of the Java Development Kit (JDK) on all
hosts. If you
are upgrading to Cloudera Manager and CDH version 6.1 and higher,
you can choose to install OpenJDK 1.8 instead of the Oracle
JDK.There two options for JDK installation:
- Manually install the Oracle JDK or OpenJDK on all hosts.
- Manually install the Oracle JDK 1.8 on the Cloudera Manager host, and then select the Install Oracle Java SE Development Kit checkbox when prompted while running the Cloudera Manager Upgrade wizard.
- If you plan to use Spark 2.2 using Cloudera Manager 5.x, you must install Oracle JDK 1.8 manually and configure the Java Home Directory property for all the hosts.
- Review the Release Notes.
- Review the Cloudera Security Bulletins.
- Downtime for the cluster is not required to complete the Cloudera Manager upgrade.
- Downtime for the cluster is not required to complete the Cloudera Manager upgrade; for services that contribute to Cloudera Navigator audits, lineage, or search, restarting the service is recommended but can be scheduled independently of the upgrade.
- Downtime for the cluster is required when upgrading to Cloudera Manager 7.1 or higher.
- If you have previously installed
Kafka 1.2, and are upgrading from Cloudera Manager 5.4 or lower,
remove the Kafka CSD:
- Determine the location of the CSD directory:
- Select .
- Click the Custom Service Descriptors category.
- Retrieve the directory from the Local Descriptor Repository Path property.
- Delete the Kafka CSD from the directory.
- Determine the location of the CSD directory:
- Upgrade Cloudera Manager using Tarballs is only supported for upgrades to 5.x and is now deprecated.
If your cluster uses Oracle for any databases, before upgrading from CDH 5 to CDH 6, check the value of the
COMPATIBLEinitialization parameter in the Oracle Database using the following SQL query:
SELECT name, value FROM v$parameter WHERE name = 'compatible'The default value is 12.2.0. If the parameter has a different value, you can set it to the default as shown in the Oracle Database Upgrade Guide.
Preparing to upgrade Cloudera Navigator
Cloudera Navigator is upgraded as part of the Cloudera Manager upgrade process. There are no additional steps required. However, to ensure that Navigator metadata is efficiently upgraded and the upgraded version performs well, make sure to check that Navigator Metadata Server is configured with the correct amount of Java heap. For information on how to determine the correct heap size and to change the heap size if necessary, see Estimating Optimal Java Heap Size for Cloudera Navigator.