Fixed Issues in Apache Kafka

Review the list of Kafka issues that are resolved in Cloudera Runtime 7.1.4.

KAFKA-9839: IllegalStateException on metadata update when broker learns about its new epoch after the controller

This is a backported fix. The broker now accepts control requests if the broker epoch is newer than the current epoch.

OPSAPS-57907: The Kafka metric collector adapter generates high CPU load

This issue is now resolved.

OPSAPS-57113: The Kafka Broker Advanced Configuration Snippet (Safety Valve) for ssl.properties does not propagate configurations correctly

Configuration containing dollar signs is now propagated correctly.

CDPD-17172: Fix of consumer group rebalance issue KAFKA-9752 backported.

This issue is now resolved.

Kafka Connect fails to communicate with secured Schema Registry

The *.converter.sasl.jaas.config connector property can now be used to specify the JAAS configuration required when connecting to a secured Schema Registry server. For example:

"value.converter.sasl.jaas.config": "com.sun.security.auth.module.Krb5LoginModule
          required useKeyTab=true storeKey=true keyTab=\"/pathToKeytab/fileName.keytab\" 
          principal=\"principal@REALM.COM\";",

If multiple Kafka Connect roles are installed, you must provide a JAAS configuration that uses a headless principal and a keytab. If a valid configuration is added, Kafka Connect will successfully communicate with the server. Creating a JAAS configuration with a RegistryClient entry and adding the file to the Kafka environment is no longer required.