Cloudera Manager 7.7.1 Cumulative hotfix 14

Know more about the Cloudera Manager 7.7.1 cumulative hotfixes 14.

This cumulative hotfix was released on September 7, 2023.

Following are the list of known issues and their corresponding workarounds that are shipped for Cloudera Manager 7.7.1 CHF14 (version: 7.7.1-h14-44760873):

OPSAPS-68689: Unable to emit the LDAP Bind password in core-site.xml for client configurations

If the CDP cluster has LDAP group to OS group mapping enabled, then applications running in Spark or Yarn would fail to authenticate to the LDAP server when trying to use the LDAP bind account during the LDAP group search.

This is because the LDAP bind password was not passed to the /etc/hadoop/conf/core-site.xml file. This was intended behavior to prevent leaking the LDAP bind password in a clear text field.

Set the LDAP Bind password through the HDFS client configuration safety valve.

On the Cloudera Manager UI, navigate to the HDFS service, by clicking on the HDFS service under the Cluster.
Click the Configuration tab. Search for the HDFS Client Advanced Configuration Snippet (Safety Valve) for hdfs-site.xml configuration parameter.
Add an entry with the following values:
- Name = hadoop.security.group.mapping.ldap.bind.password
- Value = (Enter the LDAP bind password here)
- Description = Password for LDAP bind account
Then click the Save Changes button to save the safety valve entry.
Perform the instructions from the Manually Redeploying Client Configuration Files to manually deploy client configuration files to the cluster.

OPSAPS-68452: Azul Open JDK 8 and 11 are not supported with Cloudera Manager

Azul Open JDK 8 and 11 are not supported with Cloudera Manager. To use Azul Open JDK 8 or 11 for Cloudera Manager RPM/DEBs, you must manually create a symlink between the Zulu JDK installation path and the default JDK path.

After installing Azul Open JDK8 or 11, you must run the following commands on all the hosts in the cluster:

Azul Open JDK 8

RHEL or SLES

# sudo ln -s /usr/lib/jvm/java-8-zulu-openjdk-jdk /usr/lib/jvm/java-8-openjdk

Ubuntu or Debian

# sudo ln -s /usr/lib/jvm/zulu-8-amd64 /usr/lib/jvm/java-8-openjdk

Azul Open JDK 11

For DEBs only

# sudo ln -s /usr/lib/jvm/zulu-11-amd64 /usr/lib/jvm/java-11

CDPD-75871: Hive external table replication fails after you upgrade from 7.7.1 CHF14

After you upgrade, the Hive external table replication policies fail during the “Hive import” step if the following conditions are true:

The default setting columnStatsImportMultiThreaded = true in the Cloudera Manager > Clusters > Hive service > Configuration > hive_replication_env_safety_valve property is retained after the upgrade process.
You are using HA Hive Metastore, and are using Hive and Impala to query source tables.

Perform the following steps to resolve the issue:

Go to the target Cloudera Manager > Clusters > Hive service > Configuration tab.
Locate the hive_replication_env_safety_valve property.
Add COLUMN_STATS_IMPORT_MULTI_THREADED=false, and Save the changes.
Restart the Hive service.
Run the Hive external table replication policy.

Following are the list of fixed issues that were shipped for Cloudera Manager 7.7.1 CHF14 (version: 7.7.1-h14-44760873):

OPSAPS-67641: The Next Run column on the Cloudera Manager > Replication > Replication Policies page was showing None Scheduled for recurring Hive ACID replication policy jobs, which is incorrect. The column now displays the correct message.
OPSAPS-65104: Importing table column statistics for Hive replication is thread-safe but causes performance regression.: To resolve this issue, perform the following steps:

Go to the Cloudera Manager > Clusters > Hive service > Configuration tab.

Locate the hive_replication_env_safety_valve property.

Add only one of the following key-value pair depending on your requirement:

COLUMN_STATS_IMPORT_MULTI_THREADED=true
This ensures that the column statistics import operation is multi-threaded for Hive replication.

SKIP_COLUMN_STATS_IMPORT=true
This ensures that the column statistics import is skipped entirely.

The repositories for Cloudera Manager 7.7.1-CHF14 are listed in the following table:

Table 1. Cloudera Manager 7.7.1-CHF14
Repository Type	Repository Location
RHEL 8 Compatible	Repository: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/redhat8/yum Repository File: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/redhat8/yum/cloudera-manager.repo
RHEL 7 Compatible	Repository: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/redhat7/yum Repository File: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/redhat7/yum/cloudera-manager.repo
SLES 12	Repository: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/sles12/yum Repository File: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/sles12/yum/cloudera-manager.repo
Ubuntu 20	Repository: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/ubuntu2004/apt Repository file: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/ubuntu2004/apt/cloudera-manager.list
Ubuntu 18	Repository: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/ubuntu1804/apt Repository file: https://`username`:`password`@archive.cloudera.com/p/cm7/patch/7.7.1-h14-44760873/ubuntu1804/apt/cloudera-manager.list

Cloudera Manager 7.7.1 Cumulative hotfix 14

We want your opinion

How can we improve this page?