You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jun Rao (Jira)" <ji...@apache.org> on 2022/06/03 16:13:00 UTC
[jira] [Resolved] (KAFKA-13803) Refactor Leader API Access
[ https://issues.apache.org/jira/browse/KAFKA-13803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao resolved KAFKA-13803.
-----------------------------
Fix Version/s: 3.3.0
Resolution: Fixed
merged the PR to trunk
> Refactor Leader API Access
> --------------------------
>
> Key: KAFKA-13803
> URL: https://issues.apache.org/jira/browse/KAFKA-13803
> Project: Kafka
> Issue Type: Improvement
> Reporter: Rittika Adhikari
> Assignee: Rittika Adhikari
> Priority: Major
> Fix For: 3.3.0
>
>
> Currently, AbstractFetcherThread has a series of protected APIs which control access to the Leader. ReplicaFetcherThread and ReplicaAlterLogDirsThread respectively override these protected APIs and handle access to the Leader in a remote broker leader and a local leader context.
> We propose to move these protected APIs to a LeaderEndPoint interface, which will serve all fetches from the Leader. We will implement a RemoteLeaderEndPoint and a LocalLeaderEndPoint accordingly. This change will greatly simplify our existing follower fetch code.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)