Known Issues in Apache Kafka
Learn about the known issues in Kafka, the impact or changes to the functionality, and the workaround.
Known Issues identified in Cloudera Runtime 7.3.1.400 SP2
There are no new known issues identified in this release.
Known Issues identified in Cloudera Runtime 7.3.1.300 SP1 CHF 1
There are no new known issues identified in this release.
Known Issues identified in Cloudera Runtime 7.3.1.200 SP1
There are no new known issues identified in this release.
Known Issues identified in Cloudera Runtime 7.3.1.100 CHF 1
There are no new known issues identified in this release.
Cloudera Runtime 7.3.1
- OPSAPS-59553: Streams Messaging Manager bootstrap server config should be updated based on Kafka's listeners
- 7.1.7, 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
- The
offsets.topic.replication.factor
property must be less than or equal to the number of live brokers - 7.1.7, 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
- Requests fail when sending to a nonexistent topic with
auto.create.topics.enable
set to true - 7.1.7, 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
- KAFKA-2561: Performance degradation when SSL Is enabled
- 7.1.7, 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
- RANGER-3809: Idempotent Kafka producer fails to initialize due to an authorization failure
- 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
- CDPD-49304: AvroConverter does not support composite default values
- 7.1.7, 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
- DBZ-4990: The Debezium Db2 Source connector does not support schema evolution
- 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
- CFM-3532: The Stateless NiFi Source, Stateless NiFi Sink, and HDFS Stateless Sink connectors cannot use Snappy compression
- 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
- OPSAPS-69317: Kafka Connect Rolling Restart Check fails if SSL Client authentication is required
- 7.1.9, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400
Unsupported Features
The following Kafka features are not supported in Cloudera
- Only Java and .Net based clients are supported. Clients developed with C, C++, Python, and other languages are currently not supported.
- The Kafka default authorizer is not supported. This includes setting ACLs and all related APIs, broker functionality, and command-line tools.
- SASL/SCRAM is only supported for delegation token based authentication. It is not supported as a standalone authentication mechanism.
- Kafka KRaft in this release of Cloudera Runtime is in technical
preview and does not support the following:
- Deployments with multiple log directories. This includes deployments that use JBOD for storage.
- Delegation token based authentication.
- Migrating an already running Kafka service from ZooKeeper to KRaft.
- Atlas Integration.
Limitations
- Collection of partition level metrics may cause Cloudera Manager performance to degrade
- If the Kafka service operates with a large number of
partitions, collection of partition level metrics may cause Cloudera Manager 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.