Known Issues in Streams Messaging
Learn about the known issues in Streams Messaging clusters, the impact or changes to the functionality, and the workaround.
Kafka
Learn about the known issues and limitations in Kafka in this release:
Known Issues
- The
offsets.topic.replication.factor
property must be less than or equal to the number of live brokers - The
offsets.topic.replication.factor
broker configuration is now enforced upon auto topic creation. Internal auto topic creation will fail with aGROUP_COORDINATOR_NOT_AVAILABLE
error until the cluster size meets this replication factor requirement. - Requests fail when sending to a nonexistent topic with
auto.create.topics.enable
set to true - The first few
produce
requests fail when sending to a nonexistent topic withauto.create.topics.enable
set to true. - Custom Kerberos principal names cannot be used for kerberized ZooKeeper and Kafka instances
- When using ZooKeeper authentication and a custom Kerberos principal, Kerberos-enabled Kafka does not start. You must disable ZooKeeper authentication for Kafka or use the default Kerberos principals for ZooKeeper and Kafka.
- KAFKA-2561: Performance degradation when SSL Is enabled
- In some configuration scenarios, significant performance degradation can occur when SSL is enabled. The impact varies depending on your CPU, JVM version, Kafka configuration, and message size. Consumers are typically more affected than producers.
- OPSAPS-43236: Kafka garbage collection logs are written to the process directory
- By default Kafka garbage collection logs are written to the agent process directory. Changing the default path for these log files is currently unsupported.
- CDPD-45183: Kafka Connect active topics might be visible to unauthorised users
- The Kafka Connect active topics endpoint
(
/connectors/[***CONNECTOR NAME***]/topics
) and the Connect Cluster page on the SMM UI disregard the user permissions configured for the Kafka service in Ranger. As a result, all active topics of connectors might become visible to users who do not have permissions to view them. Note that user permission configured for Kafka Connect in Ranger are not affected by this issue and are correctly applied. - OPSAPS-65485: Selecting the Require Connectors To Override Kafka Client JAAS Configuration property causes automatic Kafka Connect startup retries to fail
- If the Require Connectors To Override Kafka Client JAAS Configuration property is selected for the Kafka Connect role and the role fails to start due to any reason, all automatic retries to start the role will also fail. This is true even if the root cause of the initial startup failure was caused by an intermittent issue.
- RANGER-3809: Idempotent Kafka producer fails to initialize due to an authorization failure
- Kafka producers that have idempotence enabled require the
Idempotent Write permission to be set on the cluster resource in Ranger. If permission
is not given, the client fails to initialize and an error similar to the following is
thrown:
Idempotence is enabled by default for clients in Kafka 3.0.1, 3.1.1, and any version after 3.1.1. This means that any client updated to 3.0.1, 3.1.1, or any version after 3.1.1 is affected by this issue.org.apache.kafka.common.KafkaException: Cannot execute transactional method because we are in an error state at org.apache.kafka.clients.producer.internals.TransactionManager.maybeFailWithError(TransactionManager.java:1125) at org.apache.kafka.clients.producer.internals.TransactionManager.maybeAddPartition(TransactionManager.java:442) at org.apache.kafka.clients.producer.KafkaProducer.doSend(KafkaProducer.java:1000) at org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:914) at org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:800) . . . Caused by: org.apache.kafka.common.errors.ClusterAuthorizationException: Cluster authorization failed.
Limitations
- Collection of Partition Level Metrics May Cause Cloudera Manager’s Performance to Degrade
-
If the Kafka service operates with a large number of partitions, collection of partition level metrics may cause Cloudera Manager's performance to degrade.
If you are observing performance degradation and your cluster is operating with a high number of partitions, you can choose to disable the collection of partition level metrics.Complete the following steps to turn off the collection of partition level metrics:- Obtain the Kafka service name:
- In Cloudera Manager, Select the Kafka service.
- Select any available chart, and select Open in Chart Builder from the configuration icon drop-down.
- Find
$SERVICENAME=
near the top of the display.The Kafka service name is the value of$SERVICENAME
.
- Turn off the collection of partition level metrics:
- Go to .
- Find and configure the Cloudera Manager Agent Monitoring Advanced
Configuration Snippet (Safety Valve) configuration
property.Enter the following to turn off the collection of partition level metrics:
Replace[KAFKA_SERVICE_NAME]_feature_send_broker_topic_partition_entity_update_enabled=false
[KAFKA_SERVICE_NAME]
with the service name of Kafka obtained in step 1. The service name should always be in lower case. - Click Save Changes.
- Obtain the Kafka service name:
Schema Registry
Learn about the known issues and limitations in Schema Registry in this release:
- CDPD-48568: JAR storage does not work on AWS S3 for Schema Registry
-
If you are using AWS S3 to store the serializer and deserializer JAR files used by Schema Registry, the Schema Registry server might not be able reach these JAR files. As a result, message serialization and deserialization will not work with the affected schemas. If you are affected by this issue, class not found errors related to AWS library classes will be present in the Schema Registry server logs.
Streams Messaging Manager
- CDPD-36422: 1MB flow.snapshot freezes safari
- Importing large connector configurations/ flow.snapshots reduces the usability of the Streams Messaging Manager's Connector page when using Safari browser.
- CDPD-39313: Some numbers are not rendered properly in SMM UI
- Very large numbers can be imprecisely represented on the UI. For example, bytes larger than 8 petabytes would lose precision.
- CDPD-45183: Kafka Connect active topics might be visible to unauthorised users
- The Kafka Connect active topics endpoint
(
/connectors/[***CONNECTOR NAME***]/topics
) and the Connect Cluster page on the SMM UI disregard the user permissions configured for the Kafka service in Ranger. As a result, all active topics of connectors might become visible to users who do not have permissions to view them. Note that user permission configured for Kafka Connect in Ranger are not affected by this issue and are correctly applied. - CDPD-46465: Searching for workers on the connector overview page freezes the page
- Navigating to the SMM UI Connectors page selecting the Cluster Profile tab and filtering for hosts using the search field causes the page to freeze.
- CDPD-46728: SMM UI shows the consumerGroup instead of the instances on the Profile page's right hand side
- On the ConsumerGroupDetail page, SMM UI shows the group instead of its instances on the right hand side table.
- OPSAPS-59553: SMM's bootstrap server config should be updated based on Kafka's listeners
- SMM does not show any metrics for Kafka or Kafka Connect when multiple listeners are set in Kafka.
- OPSAPS-59597: SMM UI logs are not supported by Cloudera Manager
- Cloudera Manager does not support the log type used by SMM UI.
Streams Replication Manager
Learn about the known issues and limitations in Streams Replication Manager in this release:
- CDPD-22089: SRM does not sync re-created source topics until the offsets have caught up with target topic
- Messages written to topics that were deleted and re-created are not replicated until the source topic reaches the same offset as the target topic. For example, if at the time of deletion and re-creation there are a 100 messages on the source and target clusters, new messages will only get replicated once the re-created source topic has 100 messages. This leads to messages being lost.
- CDPD-30275: SRM may automatically re-create deleted topics on target clusters
- If
auto.create.topics.enable
is enabled, deleted topics might get automatically re-created on target clusters. This is a timing issue. It only occurs if remote topics are deleted while the replication of the topic is still ongoing.
- SRM cannot replicate Ranger authorization policies to or from Kafka clusters
- Due to a limitation in the Kafka-Ranger plugin, SRM cannot
replicate Ranger policies to or from clusters that are configured to use Ranger for
authorization. If you are using SRM to replicate data to or from a cluster that uses
Ranger, disable authorization policy synchronization in SRM. This can be achieved by
clearing the Sync Topic Acls Enabled
(
sync.topic.acls.enabled
) checkbox.
Cruise Control
Learn about the known issues and limitations in Cruise Control in this release:
- Rebalancing with Cruise Control does not work due to the metric reporter failing to report the CPU usage metric
- On the Kafka broker, the Cruise control metric reporter plugin
may fail to report the CPU usage metric.If the CPU usage metric is not reported, the numValidWindows in Cruise Control will be 0 and proposal generation as well as partition rebalancing will not work. If this issue is present, the following message will be included in the Kafka logs:
WARN com.linkedin.kafka.cruisecontrol.metricsreporter.CruiseControlMetricsReporter: [CruiseControlMetricsReporterRunner]: Failed reporting CPU util.
java.io.IOException: Java Virtual Machine recent CPU usage is not available.
This issue is only known to affect Kafka broker hosts that have the following specifications:- CPU: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
- OS: Linux 4.18.5-1.el7.elrepo.x86_64 #1 SMP Fri Aug 24 11:35:05 EDT 2018 x86_64
- Java version: 8-18
- CDPD-47616: Unable to initiate rebalance, number of valid windows (NumValidWindows) is zero
- If a Cruise Control rebalance is initiated with the
rebalance_disk
parameter and Cruise Control is configured to fetch metrics from Cloudera Manager (Metric Reporter is set to CM metrics reporter), Cruise Control stops collecting metrics from the partitions that are moved. This is because Cloudera Manager does not collect metrics from moved partitions due to an issue in Kafka (KAFKA-10320).If the metrics are not available, the partition is considered invalid by Cruise Control. This results in Cruise Control blocking rebalance operations and proposal generation.