Cloudera Upgrade Guide Companion
Welcome to the Cloudera Upgrade Guide Companion.
This upgrade guide companion will help you in achieving the key milestones for successfully completing an in-place upgrade of your cluster.
Use the My Environment section to define your cluster upgrade configuration. Use the tabs below to access key checkpoints for completing your upgrade and as a jumping off point for each individual milestone.
You can always review the complete upgrade documentation here.
You must review the supported upgrade paths information before upgrading to CDP cluster here.
You must review the supported Cloudera Manager information before upgrading to CDP cluster here.
Getting Started
Upgrading HDP to CDP
To get started with upgrading from HDP to CDP, first learn about the overall upgrade process and the impact of an upgrade on your deployment.
- HDP 2 to CDP
- HDP 3 to CDP
Upgrading CDH to CDP
To get started with upgrading from CDH to CDP, first learn about the overall upgrade process and the impact of an upgrade on your deployment.
CDH 5 to CDP
When upgrading from CDH 5.x, you should review:
CDH 6 to CDP
When upgrading from CDH 6.x, you should review
Upgrading CDP to a higher version
- Upgrading to CDP Private Cloud Base 7.1.9 SP1
-
You can upgrade to CDP 7.1.9 SP1 from the following CDP versions:
- CDP 7.1.9
- CDP 7.1.8 Latest cumulative hotfix
- CDP 7.1.7 SP3
- Upgrading to CDP Private Cloud Base 7.1.9
- You can upgrade to CDP 7.1.9 from the following CDP versions:
- Upgrading to CDP Private Cloud Base 7.1.7 SP3
-
You can upgrade to CDP 7.1.7 SP3 from the following CDP versions:
- CDP 7.1.7 SP2
- CDP 7.1.7 SP1
- CDP 7.1.7
- CDP 7.1.6
For more information on the supported upgrade paths, see Supported in-place upgrade paths. - CDP 7.1.x to a higher version of CDP
-
To get started with upgrading to a newer version of CDP, first learn about the overall upgrade process and the impact of an upgrade on your deployment. See Preparing for your upgrade
Upgrading CDP to a Serivce Pack
Upgrades to CDP Private Cloud Base 7.1.9 Service Pack 1 (SP1)
Note the following requirements for upgrades to CDP Private Cloud Base 7.1.9 SP1:
- You can upgrade to CDP 7.1.9 SP1 (7.1.9.1000) from CDP 7.1.9 or CDP 7.1.8 latest cumulative hotfix or CDP 7.1.7 SP3 (7.1.7.3000).
- You must first upgrade to Cloudera Manager 7.11.3 CHF7 or higher, which is the supported version for the CDP 7.1.9 SP1.
- You can use Cloudera Manager 7.11.3 CHF7 or higher to manage deployments where Cloudera Manager is managing a CDP Private Cloud Data Services cluster.
Upgrades to CDP Private Cloud Base 7.1.7 Service Pack 3 (SP3)
Note the following requirements for upgrades to CDP Private Cloud Base 7.1.7 SP3:
- You can upgrade to CDP 7.1.7 SP3 (7.1.7.3000) from CDP 7.1.7 SP2 (7.1.7.2000) or CDP 7.1.7 SP1 (7.1.7.1000) or CDP 7.1.7 (log4j2) or CDP 7.1.6.
- You must first upgrade to Cloudera Manager 7.11.3 CHF4 or higher, which is the supported version for the CDP 7.1.7 SP3.
- You can use Cloudera Manager 7.11.3 CHF4 or higher to manage deployments where Cloudera Manager is managing a CDP Private Cloud Data Services cluster.
Upgrades to CDP Private Cloud Base 7.1.7 Service Pack 2 (SP2)
Note the following requirements for upgrades to CDP Private Cloud Base 7.1.7 SP2:
- You can upgrade to Cloudera Runtime 7.1.7 Service Pack 2 (7.1.7.2000) from Cloudera Runtime 7.1.7 Service Pack 1 (7.1.7.1000) or Cloudera Runtime 7.1.7 (log4j2) or Cloudera Runtime 7.1.6.
- You must first upgrade to Cloudera Manager 7.6.7, which is the supported version for Service Pack 2.
- You cannot use Cloudera Manager 7.6.7 to manage deployments where Cloudera Manager is managing a CDP Private Cloud Data Services cluster.
Pre-upgrade Tasks
Gather information on your deployment and verify cluster environment readiness. You can prepare a sample data for ingestion and validate the Apache Hive constructs before you upgrade.
- CDH 5 to CDP
- The following procedures
must be completed before performing a cluster upgrade to
CDP Private Cloud Base (Cloudera Runtime 7.1.1 or higher).
Only complete the procedures for services running in your
source cluster:
- Transitioning from MapReduce 1 to MapReduce 2
- Transitioning Cloudera Search configuration before upgrading to Cloudera Runtime
- Transitioning from Sentry Policy Files to the Sentry Service
- Transitioning the Sentry service to Apache Ranger
- Transitioning Navigator content to Atlas
- Migrating Hive 1-2 to Hive 3
- Checking Apache HBase
- CDH cluster upgrade requirements for Replication Manager
- Installing dependencies for Hue before upgrading to CDP
-
- Upgrade the JDK
- Upgrade the Operating System
- You must install Python 3.8 (or 3.9 for RHEL 9.1) on all hosts before upgrading to Cloudera Manager 7.11.3. See Installing Python 3.
- After you complete these steps, continue with your upgrade by Upgrading Cloudera Manager.
- CDH 6 to CDP
- The following procedures must be completed before
performing a cluster upgrade to CDP Private Cloud Base
(Cloudera Runtime 7.1.1 or higher). Only complete the
procedures for services running in your source cluster:
- Transitioning from Sentry Policy Files to the Sentry Service
- Transitioning the Sentry service to Apache Ranger
- Transitioning Navigator content to Atlas
- Migrating Hive 1-2 to Hive 3
- Checking Apache HBase
- CDH cluster upgrade requirements for Replication Manager
- Installing dependencies for Hue before upgrading to CDP
- In addition to the
pre-upgrade steps for Cloudera Runtime services, you may
also need to do upgrade your JDK or operating system. See
the Cloudera
support Matrix for more information on supported
operating systems and JDKs.
- Upgrade the JDK
- Upgrade the Operating System
- You must install Python 3.8 (or 3.9 for RHEL 9.1) on all hosts before upgrading to Cloudera Manager 7.11.3. See Installing Python 3.
- You must install Python 3.10 for SLES 15 SP4 and SLES 15 SP5 on all hosts before upgrading to Cloudera Manager 7.11.3 CHF7. See Installing Python 3.
- After you complete these steps, continue with your upgrade by Upgrading Cloudera Manager.
- CDP to a higher version of CDP
- You may need to upgrade your JDK or
operating system. See the Cloudera
support Matrix for more information on supported
operating systems and JDKs.
- Upgrade the JDK
- Upgrade the Operating System
- You must install Python 3.8 (or 3.9 for RHEL 9.1) on all hosts before upgrading to Cloudera Manager 7.11.3. See Installing Python 3.
- You must install Python 3.10 for SLES 15 SP4 and SLES 15 SP5 on all hosts before upgrading to Cloudera Manager 7.11.3 CHF7. See Installing Python 3.
- After you complete these steps, continue with your upgrade by Upgrading Cloudera Manager.
- CDP to a higher version of CDP
- You may need to upgrade your JDK or
operating system. See the Cloudera
support Matrix for more information on supported
operating systems and JDKs.
- Upgrade the JDK
- Upgrade the Operating System
- You must install Python 3.8 (or 3.9 for RHEL 9.1) on all hosts before upgrading to Cloudera Manager 7.11.3. See Installing Python 3.
- You must install Python 3.10 for SLES 15 SP4 and SLES 15 SP5 on all hosts before upgrading to Cloudera Manager 7.11.3 CHF7. See Installing Python 3.
- After you complete these steps, continue with your upgrade by Upgrading Cloudera Manager.
Upgrade the Cluster
Plan how and when to begin your upgrade. Check readiness and upgrade Ambari and HDP. Transition from HDP to Cloudera Manager.
- HDP 2 to CDP
-
Upgrade Ambari here
Upgrade HDP here
Pre-Transition steps here
Cloudera Manager Installation here
Installing JDBC driver here
Transitioning HDP 2.6.5 cluster to CDP Private Cloud Base cluster using the AM2CM tool here
- HDP 3 to CDP
-
Upgrade Ambari here
Upgrade HDP here
Pre-Transition steps here
Cloudera Manager Installation here
Installing JDBC driver here
Transitioning HDP 3.1.5 cluster to CDP Private Cloud Base cluster using the AM2CM tool here
CDH 5 to CDP
Upgrading a cluster requires some preparatory steps such as backing up your cluster and Cloudera Manager, establishing access to the software, and other tasks.
Before upgrading your cluster(s) you must first upgrade Cloudera Manager to a version that supports your planned cluster upgrades. See Upgrade Cloudera Manager.
For detailed procedures, see Upgrading a Cluster.
CDH 6 to CDP
Upgrading a cluster requires some preparatory steps such as backing up your cluster and Cloudera Manager, establishing access to the software, and other tasks.
Before upgrading your cluster(s) you must first upgrade Cloudera Manager to a version that supports your planned cluster upgrades. See Upgrade Cloudera Manager.
For detailed procedures, see Upgrading a Cluster.
- CDP to a higher version of CDP
- Upgrading a cluster requires some preparatory steps such
as backing up your cluster and Cloudera Manager,
establishing access to the software, and other tasks.
Before upgrading your cluster(s) you must first upgrade Cloudera Manager to a version that supports your planned cluster upgrades. See Upgrade Cloudera Manager.
For detailed procedures, see Upgrading a Cluster.
- CDP to a higher version of CDP
- Upgrading a cluster requires some preparatory steps such
as backing up your cluster and Cloudera Manager,
establishing access to the software, and other tasks.
Before upgrading your cluster(s) you must first upgrade Cloudera Manager to a version that supports your planned cluster upgrades. See Upgrade Cloudera Manager.
For detailed procedures, see Upgrading a Cluster.
Post-Upgrade Tasks
If you have LDAP configured on your cluster, configure external authentication with Cloudera Manager. You can also install additional services like DAS and Hue. Test your applications and services on your cluster.
- HDP 2 to CDP
-
Post Transition Steps here
Configuring External for Cloudera Manager here
Installing DAS on CDP Private Cloud Base here
Adding Hue service with Cloudera Manager here
- HDP 3 to CDP
-
Post Transition Steps here
Configuring External for Cloudera Manager here
Installing DAS on CDP Private Cloud Base here
Adding Hue service with Cloudera Manager here
CDH 5 to CDP
The following procedures must be completed after performing a cluster upgrade to CDP Private Cloud Base (Cloudera Runtime 7.1.1 or higher). Only complete the procedures for services running in your source cluster:
- Update permissions for Replication Manager service
- Apache Hive Expedited Migration Tasks
- Apache Hive Changes in CDP
- Apache Hive Post-Upgrade Tasks
- Hue Post-Upgrade Tasks
- Apache Impala changes in CDP
- Sentry to Ranger Permissions
- Migrating ACLs from Key Trustee KMS to Ranger KMS
- Cloudera Search post-upgrade tasks
- Apache Hadoop YARN default value changes
- Upgrade Notes for Apache Kudu 1.12 / CDP 7.1
- Apache HBase post-upgrade tasks
- Configure SMM to monitor SRM replications
- Configure SMM's service dependency on Schema Registry
- Apache Sqoop Changes
CDH 6 to CDP
The following procedures must be completed after performing a cluster upgrade to CDP Private Cloud Base (Cloudera Runtime 7.1.1 or higher). Only complete the procedures for services running in your source cluster:
- Update permissions for Replication Manager service
- Apache Hive Expedited Migration Tasks
- Apache Hive Changes in CDP
- Apache Hive Post-Upgrade Tasks
- Hue Post-Upgrade Tasks
- Apache Impala changes in CDP
- Sentry to Ranger Permissions
- Apache Hadoop YARN default value changes
- Upgrade Notes for Apache Kudu 1.12 / CDP 7.1
- Apache HBase post-upgrade tasks
- Configure SMM to monitor SRM replications
- Configure SMM's service dependency on Schema Registry
- Apache Sqoop Changes
- CDP to a higher version of CDP
- CDP to a higher version of CDP
Troubleshooting
You can review a list of possible causes and solutions to debug and resolve issues that you might face.
- HDP to CDP
-
Post-upgrade HDP 2 Troubleshooting DAS Installation
Post-upgrade HDP 3 Troubleshooting DAS Installation
CDH 5 to CDP
If you need to review common things to check that you may have missed during your upgrade, review troubleshooting suggestions here.
CDH 6 to CDP
If you need to review common things to check that you may have missed during your upgrade, review troubleshooting suggestions here.
- CDP to CDP
- See Troubleshooting.
- CDP to CDP
- See Troubleshooting.