[jira] [Resolved] (KAFKA-16410) kafka-leader-election / LeaderElectionCommand doesn't set exit code on error

[ https://issues.apache.org/jira/browse/KAFKA-16410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16410. Fix Version/s: 3.8.0 Resolution: Fixed > kafka-leader-election / LeaderElectionComm

Re: KRaft Observer Nodes

Hi Sanaa, in KRaft mode there is the role of "observer" which is typically taken by brokers as part of the data plane. The broker/observer can discover which node is the leader/active controller and fetches the metadata from it (as the "followers" in the KRaft quorum), but cannot vote and cannot be

KRaft Observer Nodes

Hello, Currently in Zookeeper, there is the concept of an observer/dummy node that can be used when scaling up a cluster ( https://zookeeper.apache.org/doc/r3.4.13/zookeeperObservers.html). Is there an equivalent of an observer node in KRaft mode? Asking because we use the observer node for our s

[jira] [Created] (KAFKA-16415) Make sure all subclass of CommandDefaultOptions can process "--help" and "–version"

Chia-Ping Tsai created KAFKA-16415: -- Summary: Make sure all subclass of CommandDefaultOptions can process "--help" and "–version" Key: KAFKA-16415 URL: https://issues.apache.org/jira/browse/KAFKA-16415

[jira] [Created] (KAFKA-16414) Inconsistent active segment expiration behavior between retention.ms and retention.bytes

Kuan Po Tseng created KAFKA-16414: - Summary: Inconsistent active segment expiration behavior between retention.ms and retention.bytes Key: KAFKA-16414 URL: https://issues.apache.org/jira/browse/KAFKA-16414