You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "HaiyuanZhao (Jira)" <ji...@apache.org> on 2021/07/04 03:49:00 UTC

[jira] [Commented] (KAFKA-13006) Remove the method RaftClient.leaderAndEpoch

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

HaiyuanZhao commented on KAFKA-13006:
-------------------------------------

Hi, [~jagsancio]

According to my understanding, If we remove the method {{RaftClient.leaderAndEpoch, then all the instances which implements RaftClient.}}{{leaderAndEpoch must register a RaftClient listenr to get the latest valid leader?}}{{}}

> Remove the method RaftClient.leaderAndEpoch
> -------------------------------------------
>
>                 Key: KAFKA-13006
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13006
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jose Armando Garcia Sancio
>            Assignee: HaiyuanZhao
>            Priority: Major
>
> The are semantic differences between {{RaftClient.leaderAndEpoch}} and {{RaftClient.Listener.handleLeaderChange}} specially when the raft client transition from follower to leader. To simplify the API, I think that we should remove the method {{RaftClient.leaderAndEpoch}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)