Known Issues in Streams Messaging

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 a GROUP_COORDINATOR_NOT_AVAILABLE error until the cluster size meets this replication factor requirement.

None

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 with auto.create.topics.enable set to true.

Increase the number of retries in the producer configuration setting retries.

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.

None

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.

Configure brokers and clients with ssl.secure.random.implementation = SHA1PRNG. It often reduces this degradation drastically, but its effect is CPU and JVM dependent.

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.

None

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.

None.

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.

Review the Kafka connect logs and resolve the root cause of the startup failure. Once the issue is resolved, restart the Kafka Connect role manually. Alternatively, clear the Require Connectors To Override Kafka Client JAAS Configuration property.

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:

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.

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.

This issue has two workarounds, do either of the following:

• Explicitly disable idempotence for the producers. This can be done by setting enable.idempotence to false.
• Update your policies in Ranger and ensure that producers have Idempotent Write permission on the cluster resource.

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:

1. Obtain the Kafka service name:
   1. In Cloudera Manager, Select the Kafka service.
   2. Select any available chart, and select Open in Chart Builder from the configuration icon drop-down.
   3. Find $SERVICENAME= near the top of the display.
      The Kafka service name is the value of $SERVICENAME.
2. Turn off the collection of partition level metrics:
   1. Go to Hosts > Hosts Configuration.
   2. 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:

      [KAFKA_SERVICE_NAME]_feature_send_broker_topic_partition_entity_update_enabled=false
      

      Replace [KAFKA_SERVICE_NAME] with the service name of Kafka obtained in step 1. The service name should always be in lower case.
   3. Click Save Changes.

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.

Ensure that the aws-java-sdk-bundle-[***VERSION***].jar file is available in /opt/cloudera/parcels/CDH/lib/schemaregistry/hadoop-plugin/hadoop-schema-registry-plugin-impl/. This is the location that contains all the JAR files for the Hadoop plugin classpath.

1. Find the aws-java-sdk-bundle-[***VERSION***].jar file.
   The file is located in the folder that contains all common JAR files for parcels. You can find it using the following command:

   find /opt/cloudera/parcels/CDH/jars -iname '*aws-java-sdk-bundle*.jar

   The output of the command lists multiple versions. Take note of the latest version. For example:

   /opt/cloudera/parcels/CDH/jars/aws-java-sdk-bundle-1.12.316.jar

2. Create a symlink in /opt/cloudera/parcels/CDH/lib/schemaregistry/hadoop-plugin/hadoop-schema-registry-plugin-impl/ that points to the aws-java-sdk-bundle-[***VERSION***].jar. For example:

   ln -s /opt/cloudera/parcels/CDH/jars/aws-java-sdk-bundle-1.12.316.jar /opt/cloudera/parcels/CDH/lib/schemaregistry/hadoop-plugin/hadoop-schema-registry-plugin-impl/aws-java-sdk-bundle-1.12.316.jar

3. Restart the Schema Registry service.

Streams Messaging Manager

Streams Replication Manager

Learn about the known issues and limitations in Streams Replication Manager in this release:

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

Move the broker to a different machine where the CPU is different. This can be done by performing a manual repair on the affected nodes. For more information, see the Data Hub documentation.

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.

Configure Cruise Control to use to use the Cruise Control metrics reporter (default). This issue is not present if this metric reporter is used.

1. In Cloudera Manager, select the Cruise Control service.
2. Go to Configuration.
3. Find the Metric Reporter property.
4. Select the Cruise Control metrics reporter option.
5. Restart the Cruise Control service.