Cloudera Docs

Cloudera Manager 7.11.0-h8

Know more about the Cloudera Manager 7.11.0-h8 hotfix version which is a corresponding Cloudera Manager hotfix version for Cloudera Runtime 7.2.17.800 service pack release.

This cumulative hotfix was released on October 31, 2024.

Following are the list of fixed issues that were shipped for Cloudera Manager 7.11.0-h8 (version: 7.11.0-h8-57918262):
OPSAPS-71005: RemoteCmdWork is using a singlethreaded executor

By default, Replication Manager runs the remote commands for a replication policy through a single-thread executor. You can search and enable the enable_multithreaded_remote_cmd_executor property in the target Cloudera Manager > Administration > Settings page to run future replication policies through the multi-threaded executor. This action improves the processing performance of the replication workloads.

Additionally, you can also change the multithreaded_remote_cmd_executor_max_threads and multithreaded_remote_cmd_executor_keepalive_time properties to fine-tune the replication policy performance.
OPSAPS-69996: HBase snapshot creation in Cloudera Manager works as expected
During the HBase snapshot creation process, the snapshot create command sometimes tries to create the same snapshot twice because of an unhandled OptimisticLockException during the database write operation. This resulted in intermittent HBase snapshot creation failures. The issue is fixed now.
OPSAPS-66459: Enable concurrent Hive external table replication policies with the same cloud root
When the HIVE_ALLOW_CONCURRENT_REPLICATION_WITH_SAME_CLOUD_ROOT_PATH feature flag is enabled, Replication Manager can run two or more Hive external table replication policies with the same cloud root path concurrently.

For example, if two Hive external table replication policies have s3a://bucket/hive/data as the cloud root path and the feature flag is enabled, Replication manager can run these policies concurrently.

By default, this feature flag is disabled. To enable the feature flag, contact your Cloudera account team.

OPSAPS-69782: HBase replication policies work as expected when the peer Cloudera Manager’s API version is higher than the local cluster’s API version
HBase replication using HBase replication policies between two Data Hubs/COD clusters would fail if all the following conditions are true:
  • The destination Data Hub/COD cluster’s Cloudera Manager version is 7.9.0-h7 through 7.9.0-h9 or 7.11.0-h2 through 7.11.0-h4, or 7.12.0.0.
  • The source Data Hub/COD cluster’s Cloudera Manager major version is higher than the destination cluster’s Cloudera Manager major version.
  • The Initial Snapshot option is chosen during the HBase replication policy creation process and/or the source cluster is already participating in another HBase replication setup as a source or destination with a third cluster.
This issue is resolved.

The repositories for Cloudera Manager 7.11.0-h8 are listed in the following table:

Table 1. Cloudera Manager 7.11.0-h8
Repository Type Repository Location
RHEL 8 Compatible Repository:
https://username:password@archive.cloudera.com/p/cm-public/7.11.0-h8-57918262/redhat8/yum
Repository File:
https://username:password@archive.cloudera.com/p/cm-public/7.11.0-h8-57918262/redhat8/yum/cloudera-manager.repo
RHEL 7 Compatible Repository:
https://username:password@archive.cloudera.com/p/cm-public/7.11.0-h8-57918262/redhat7/yum
Repository File:
https://username:password@archive.cloudera.com/p/cm-public/7.11.0-h8-57918262/redhat7/yum/cloudera-manager.repo