You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2026/10/28 03:56:00 UTC

[jira] [Commented] (KAFKA-21378) Add "leaderEpoch" field in PartitionChangeRecord

    [ https://issues.apache.org/jira/browse/KAFKA-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133372#comment-18133372 ] 

Luke Chen commented on KAFKA-21378:
-----------------------------------

[~christo_lolov] , thanks for interesting in this feature. This task is needed and can be started first. I assigned to you first, but if you are not interested or don't want to take it, just let me know. Thank you.

> Add "leaderEpoch" field in PartitionChangeRecord
> ------------------------------------------------
>
>                 Key: KAFKA-21378
>                 URL: https://issues.apache.org/jira/browse/KAFKA-21378
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Luke Chen
>            Assignee: Christo Lolov
>            Priority: Major
>
> To support "bumpLeaderEpoch" RPC in the future, we should add a "leaderEpoch" field in PartitionChangeRecord, and move the leader epoch calculation logic from currently each node calculate the leader epoch when replying PartitionChangeRecord in PartitionRegistration class, to each time the PartitionChangeRecord creates, and each node only needs to take the leaderEpoch in the PartitionChangeRecord.
>  
> We should also consider the backward compatibility in this change.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)