Known Issues

SSL handshake failures

In Cloudera Data Services on premises environments, telemetry agent pods, such as database producer in Cloudera Data Warehouse or dbus-wxml-client in Cloudera Data Engineering can encounter an SSLHandshakeException when communicating with the DBus API. The pod logs display a PKIX path building failed error.

Cloudera Data Warehouse

Download the fix_cdw_ssl.py script
Export the kubeconfig env variable. Run the command export KUBECONFIG=/path/to/kube.yaml
Within the Kubernetes cluster, run the command python3 fix_cdw_ssl.py --namespace [***NAMESPACE***]. For example, python3 fix_cdw_ssl.py --namespace warehouse-xodjvg-env

The script downloads the DBus API SSL certificate and adds it to the databus-producer truststore.

Cloudera Data Engineering

Download the fix_cde_ssl.py script
Export the kubeconfig env variable. Run the command export KUBECONFIG=/path/to/kube.yaml
Within the Kubernetes cluster, run the command python3 fix_cde_ssl.py --namespace [***NAMESPACE***]. For example, python3 fix_cde_ssl.py --namespace dex-base-pc74hb7x

The script downloads the DBus API SSL certificate and adds it to the databus-producer truststore.

Impala does not support super user configuration for the observability user for Apache Ranger-enabled cluster

The observability user requires full privileges on the Observability cluster. Required services such as Kafka, HDFS, HBase, and Hive support super user setup by specifying the ranger.plugin.[service].super.users property to observability. However, this super user setup is not supported for Impala.

Manually add a new user named observability in Apache Ranger and assign full privileges.

For information, see Adding a user in Cloudera Base on premises documentation.
For information on granting user access using Apache Ranger, see Impala Authorization in Cloudera Data Warehouse Runtime for Cloudera on premises documentation.

Exporting of Impala queries fail for Telemetry Publisher with Cloudera Manager 7.11.3

Telemetry Publisher for Impala queries does not work with Cloudera Manager 7.11.3

Upgrade Cloudera Manager from 7.11.3 to 7.11.3 cumulative hotfix 6 (CHF6) version to successfully export Impala queries.

Auto Action trigger for Impala Engine

Impala Auto Action triggers do not work for the Kerberos-enabled Private Cloud base cluster running on Cloudera Manager 7.9.5 and 7.11.3.

Upgrade Cloudera Manager to 7.11.3 cumulative hotfix 9 (CHF9) version.

Telemetry publisher test altus connection fails for Cloudera Manager 7.11.3 hotfix (CHF6, 7, and 8) versions

Test connection fails with the following error:

Exception in thread "main" java.lang.NoSuchMethodError: 'com.google.common.collect.ImmutableSet com.google.common.collect.ImmutableSet.copyOf(java.util.Collection)'
	at com.cloudera.cdp.http.HttpCodesRetryChecker.<init>(HttpCodesRetryChecker.java:57)
	at com.cloudera.cdp.client.CdpClientConfigurationBuilder.<init>(CdpClientConfigurationBuilder.java:53)
	at com.cloudera.cdp.client.CdpClientConfigurationBuilder.defaultBuilder(CdpClientConfigurationBuilder.java:400)
	at com.cloudera.cdx.client.TestDatabusConnection.main(TestDatabusConnection.java:55)

This issue only affects the test connection method.

Upgrade Cloudera Manager to 7.11.3 cumulative hotfix 9 (CHF9) version, and then start Telemetry Publisher.

Limitations of Cloudera Observability Spark processing

Spark event log processing is skipped under the following conditions:

The event log size exceeds 20 GB.
The number of Spark jobs in the Spark application exceeds 500.
The number of SQL executions in the Spark application exceeds 500.
When spark.history.fs.eventLog.rolling.maxFilesToRetain is set, Spark keeps only recent event log files as configured inspark.history.fs.eventLog.rolling.maxFilesToRetain and older event log files are compacted (in a file with .compact extension). Spark event log processing of such Spark applications are skipped by Cloudera Observability.