[
https://issues.apache.org/jira/browse/KAFKA-16121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807040#comment-17807040
]
Ismael Juma commented on KAFKA-16121:
-------------------------------------
It's a bit odd to mark this as a duplicate of KAFKA-16120 given that the
descriptions are different. I understand that both issues were fixed by the
same PR, but we should either update the description of KAFKA-16120 or mark
this one as FIXED (instead of duplicate).
> Partition reassignments in ZK migration dual write mode stalled until leader
> epoch incremented
> ----------------------------------------------------------------------------------------------
>
> Key: KAFKA-16121
> URL: https://issues.apache.org/jira/browse/KAFKA-16121
> Project: Kafka
> Issue Type: Bug
> Reporter: David Mao
> Assignee: David Mao
> Priority: Major
> Fix For: 3.7.0
>
>
> I noticed this in an integration test in
> https://github.com/apache/kafka/pull/15184
> In ZK mode, partition leaders rely on the LeaderAndIsr request to be notified
> of new replicas as part of a reassignment. In ZK mode, we ignore any
> LeaderAndIsr request where the partition leader epoch is less than or equal
> to the current partition leader epoch.
> In KRaft mode, we do not bump the leader epoch when starting a new
> reassignment, see: `triggerLeaderEpochBumpIfNeeded`. This means that the
> leader will ignore the LISR request initiating the reassignment until a
> leader epoch bump is triggered through another means, for instance preferred
> leader election.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
