このコンテンツは選択した言語では利用できません。
Chapter 8. Known issues
Known issues for Streams for Apache Kafka 3.1 on RHEL.
8.1. Apache Kafka リンクのコピーリンクがクリップボードにコピーされました!
A summary of known issues for Apache Kafka.
8.1.1. Intra-broker log directory reassignment can cause a log directory to go offline リンクのコピーリンクがクリップボードにコピーされました!
When using multiple log directories per broker (JBOD) and performing intra-broker log directory reassignment (moving replicas between log directories on the same broker), Apache Kafka can incorrectly mark a log directory as failed if a transient filesystem or I/O error occurs during the operation.
This issue is caused by a race condition between background log flush operations and file deletion during replica movement. Under these conditions, Kafka may encounter a NoSuchFileException or a related I/O error and treat it as a fatal storage failure. As a result, the broker takes the entire log directory offline to protect data integrity, and any partitions stored on that directory become unavailable. The log directory can remain marked as failed even after the reassignment completes.
This behavior affects intra-broker log directory reassignment only. Inter-broker partition reassignment is not affected.
Workaround
Restart the affected Kafka broker. On restart, the broker re-scans the log directories and marks the disk as healthy if no underlying filesystem issue is present.
This is a known issue in Apache Kafka. Work to address this issue is being tracked in the Apache Kafka issue tracker (KAFKA-19571). A fix will be included in a future release of Red Hat Streams for Apache Kafka once it is available in the underlying Apache Kafka distribution.
8.1.2. Enabling eligible.leader.replicas.version リンクのコピーリンクがクリップボードにコピーされました!
A change in Apache Kafka 4.0.0 introduces restrictions on how the min.insync.replicas configuration is managed when the Eligible Leader Replicas (ELR) feature is enabled by setting eligible.leader.replicas.version to 1.
ELR is disabled by default. Enabling ELR without understanding these restrictions can lead to configuration reconciliation issues or cluster instability.
When ELR is enabled, the behavior of min.insync.replicas changes as follows:
Cluster-level (default):
- Cannot be removed
- Changing it will clear ELR configuration from all topics
Broker-level:
- Ignored entirely
- You cannot change it
-
It is recommended to remove all broker-level
min.insync.replicasbefore enabling ELR
Topic-level:
-
Changing
min.insync.replicasclears the ELR configuration for that topic
-
Changing
Workaround
Only set eligible.leader.replicas.version to 1 if you have a specific use case that requires it.
If you must use ELR:
-
Remove all broker-level
min.insync.replicasconfigurations. These settings are ignored when ELR is enabled but can lead to reconciliation errors and, in some cases, leaderless partitions during rolling updates or broker restarts. - Avoid changing the cluster-level default unless you intend to remove ELR configuration from all topics.
- Avoid changing the topic-level configuration unless you want to remove ELR configuration from that topic.
8.2. Streams for Apache Kafka リンクのコピーリンクがクリップボードにコピーされました!
A summary of known issues for Streams for Apache Kafka.
8.2.1. JMX authentication when running in FIPS mode リンクのコピーリンクがクリップボードにコピーされました!
When running Streams for Apache Kafka in FIPS mode with JMX authentication enabled, clients may fail authentication. To work around this issue, do not enable JMX authentication while running in FIPS mode. We are investigating the issue and working to resolve it in a future release.
8.3. Kafka Bridge リンクのコピーリンクがクリップボードにコピーされました!
There are no new or existing known issues for the Kafka Bridge.