What's New in Cloudera Manager 7.13.1

Learn about the new features and changed behavior of Cloudera Manager in Cloudera Manager 7.13.1 release.

You must be aware of the additional functionalities and improvements to features of Cloudera Manager in Cloudera Manager 7.13.1. Learn how the new features and improvements benefit you.

New features

Multi Python (Python 3.8 and 3.9) Support for RHEL 8

Cloudera Manager now supports both Python 3.8 and Python 3.9 for RHEL8, providing users with an easy migration path. This support allows users to upgrade to Python 3.9 seamlessly by simply installing Python 3.9 and restarting the Cloudera Manager Agents, with Cloudera Manager automatically detecting and using the highest available Python version.

By maintaining support for both versions, users can upgrade without disrupting cluster operations, ensuring smooth transitions with minimal downtime. This upgrade path helps users stay secure with up-to-date features, security patches, and performance improvements, ensuring their clusters remain stable and future-proof.

For RHEL 8.8 and RHEL 8.10, Cloudera recommends you to install Python 3.9 before upgrading Cloudera Manager to 7.13.1 version to ensure smooth transition with minimal downtime. For information about migrating from Python 3.8 to Python 3.9, see Migrating from Python 3.8 to Python 3.9 on RHEL 8.8 or RHEl 8.10.

cgroup v2 support on RHEL 9 for Cloudera Manager 7.13.1

Cloudera Manager now supports cgroup v2. cgroup v2 offers a unified hierarchy for managing system resources, making it simpler and more efficient compared to cgroup v1. For more information, see Linux Control Groups (cgroups).

You must migrate from cgroup v1 to cgroup v2 for managing the cluster resources using cgroup v2 resource allocation configuration parameters. For information about migrating to cgroup v2, see Migrating from cgroup v1 to cgroup v2.

important

Ubuntu 22 is not supported with cgroup v2.
For the users using RHEL 9.x with Cloudera Manager version lower than 7.13.1, must disable cgroup v2 if already enabled before upgrading to Cloudera Manager 7.13.1 version as cgroup v2 is not supported with Cloudera Manager version lower than 7.13.1.
During major OS upgrades, while upgrading from Redhat 8 (defaults to cgroup v1) to Redhat 9 (defaults to cgroup v2), the resource configurations will not be automatically transferred such as value of Cgroup V1 CPU Shares will not be populated in Cgroup V2 CPU Weight. Also, the controller files inside the process directories will be created under cgroups root path with default values.
If you are setting cgroup v1 parameter values manually, then you should now set cgroup v2 parameter values manually (performing conversion of values manually) and restart the services using cgroups.

Note that Cloudera Manager UI will have old values under cgroup v1 parameters which you can use as a reference to re-configure the values in the case of cgroup v2.

Enhancements to the Observability page

The following changes have been made to the Observability page::

Added role-specific metrics to the Status and Charts Library tabs for component servers such as Pipelines, ADB, and SDX.
Added relevant metrics across all Observability component servers to the Status and Charts Library tabs for the Observability page.

Implemented support for Ranger Plugin Secure Auditing in Solr using Zookeeper.

Support has been added for Ranger plugin secure auditing in Solr by using ZooKeeper.

Added Zookeeper SSL connection support for Ranger & Ranger Raz

Support has been added for ZooKeeper SSL connection for Ranger and Ranger RAZ.

Enhancements to Iceberg replication policies in Replication Manager

The following changes are available for Iceberg replication policies in Replication Manager:

Added the following options to use during the Iceberg replication policy creation process:
- JVM Options for Export - You can enter comma-separated JVM options to use for the export process during the Iceberg replication policy run.
- JVM Options for XFer - You can enter comma-separated JVM options to use for the transfer process during the Iceberg replication policy.
- JVM Options for Sync - You can enter comma-separated JVM options to use for the sync process during the Iceberg replication policy.
Iceberg replication policies can replicate V1 and V2 Iceberg tables created using Hive.