Upgrading to Cloudera Runtime 7.3.1
Cloudera Runtime 7.3.1 introduces significant new features and improvements. As a result, if you are planning to upgrade the Cloudera Runtime version in your existing Data Lake or Cloudera Data Hub clusters to 7.3.1, you might be required to perform this in multiple steps.
Some of the important Cloudera Runtime 7.3.1 features include:
- Unified Runtime for Cloudera Public Cloud and Cloudera Private Cloud.
- RHEL 8.10 is set as the default operating system.
- Python 3.9 is set as the new default version.
- OpenJDK 17 becomes the new default Java runtime version, new clusters will be launched with
this version.
OpenJDK 11 is no longer supported, and OpenJDK 11 clusters cannot be upgraded to Cloudera Runtime 7.3.1.
After upgrading clusters from Cloudera Runtime 7.2.x to 7.3.1, the JDK version remains the same, that is, JDK8.
- Spark 2 applications need to be rebased to Spark 3 as Spark 2 is no longer supported and clusters with Spark 2 will not be allowed to upgrade to Cloudera Runtime 7.3.1.
- Zeppelin service is turned off for Cloudera Runtime 7.3.1 clusters and gets removed automatically during the upgrade.
- Cloudera Data Engineering 1.23 and earlier versions are not supported on Cloudera Runtime 7.3.1
- 7.2.17.200
- 7.2.17.300
- 7.2.17.400
- 7.2.17.500
- 7.2.18.0
- 7.2.18.100
- 7.2.18.200
If your Cloudera Runtime version is not in the list of supported versions for a direct upgrade, it is possible that you can still upgrade to one of the above versions first, and then upgrade to Cloudera Runtime 7.3.1. For more information on these upgrade paths, see Identify your upgrade path.
Currently, there is no supported upgrade path to Cloudera Runtime 7.3.1 in the following cases:
- from Cloudera Runtime 7.2.18.300 or later version
- if the cluster uses JDK 11