[
https://issues.apache.org/jira/browse/KAFKA-15109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-15109:
---------------------------------
Description:
KAFKA-15021 introduced a new controller behavior that avoids increasing the
leader epoch during the controlled shutdown scenario. This prevents some
unnecessary thrashing of metadata and threads on the brokers and clients.
While a cluster is in a KIP-866 migration and has a KRaft controller with ZK
brokers, we cannot employ this leader epoch bump avoidance. The ZK brokers must
have the leader epoch bump in order for ReplicaManager to react to the
LeaderAndIsrRequest.
was:
KAFKA-15021 introduced a new controller behavior that avoids increasing the
leader epoch during the controlled shutdown scenario. This prevents some
unnecessary thrashing of metadata and threads on the brokers and clients.
While a cluster is in a KIP-866 migration and has a KRaft controller with ZK
brokers, we cannot employ this leader epoch bump avoidance. The ZK brokers must
have the leader epoch bump in order for the ISR expansion to complete.
> ISR not expanding on ZK brokers during migration
> ------------------------------------------------
>
> Key: KAFKA-15109
> URL: https://issues.apache.org/jira/browse/KAFKA-15109
> Project: Kafka
> Issue Type: Bug
> Components: kraft, replication
> Affects Versions: 3.5.0
> Reporter: David Arthur
> Priority: Critical
>
> KAFKA-15021 introduced a new controller behavior that avoids increasing the
> leader epoch during the controlled shutdown scenario. This prevents some
> unnecessary thrashing of metadata and threads on the brokers and clients.
> While a cluster is in a KIP-866 migration and has a KRaft controller with ZK
> brokers, we cannot employ this leader epoch bump avoidance. The ZK brokers
> must have the leader epoch bump in order for ReplicaManager to react to the
> LeaderAndIsrRequest.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
