Starting from Apache Kafka 4.0, Eligible Leader Replicas (KIP-966 Part 1) is available for the users to an improvement to Kafka replication (ELR is enabled by default on new clusters starting 4.1). As the “strict min ISR” rule has been generally applied, which means the high watermark for the data partition can’t advance if the size of the ISR is smaller than the min ISR(min.insync.replicas
), it makes some replicas that are not in the ISR safe to become the leader. The KRaft controller stores such replicas in the PartitionRecord field called Eligible Leader Replicas
. During the leader election, the controller will select the leaders with the following order:
The ELR is not enabled by default for 4.0. To enable the new protocol on the server, set eligible.leader.replicas.version=1
. After that the upgrade, the KRaft controller will start tracking the ELR.
Downgrades are safe to perform by setting eligible.leader.replicas.version=0
.
The ELR fields can be checked through the API DescribeTopicPartitions. The admin client can fetch the ELR info by describing the topics.
Note that when the ELR feature is enabled:
min.insync.replicas
config will be added if there is not any. The value is the same as the static config in the active controller.min.insync.replicas
config at the cluster-level is not allowed.min.insync.replicas
is updated, even if the value is unchanged, all the ELR state will be cleaned.min.insync.replicas
value at the broker-level config will be removed. Please set at the cluster-level if necessary.min.insync.replicas
config at the broker-level is not allowed.min.insync.replicas
is updated for a topic, the ELR state will be cleaned.Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.