Known Issues
Current known issues and limitations in Cloudera Observability On-Premises.
- 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.
- /cloudera-sigma-olap directory consumes significant storage space in HDFS
- 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
- 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.
- Full log link fails to open the log details page on Mozilla Firefox
- On the Spark Job Details page, clicking the Full Log link does not open the Log details page. This issue occurs on Mozilla Firefox.
- 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.
- Workload alerts missing or Kafka connection error in Admin API logs with TLS enabled
- Admin API server starts, however, the following warning is
displayed in the role
logs:
WARN org.apache.kafka.clients.NetworkClient: [kafka-producer-network-thread | producer-1] [Producer clientId=producer-1] Connection to node -1 (example-1.esc12345.root.comops.site/192.0.2.0:24) terminated during authentication. This may happen due to any of the following reasons: (1) Authentication failed due to invalid credentials with brokers older than 1.0.0, (2) Firewall blocking Kafka TLS traffic (eg it may only allow HTTPS traffic), (3) Transient network issue. WARN org.apache.kafka.clients.NetworkClient: [kafka-producer-network-thread | producer-1] [Producer clientId=producer-1] Bootstrap broker example-1.esc12345.root.comops.site:24 (id: -1 rack: null) disconnected
This issue occurs when SSL Truststore path (JKS) and password are not configured for the Admin API Server component.