[jira] [Resolved] (RATIS-1392) Cache leader information in RaftClientImpl

["Shashikant Banerjee (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RATIS-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shashikant Banerjee resolved RATIS-1392.
----------------------------------------
    Fix Version/s: 1.1.0
       Resolution: Fixed

> Cache leader information in RaftClientImpl
> ------------------------------------------
>
>                 Key: RATIS-1392
>                 URL: https://issues.apache.org/jira/browse/RATIS-1392
>             Project: Ratis
>          Issue Type: Improvement
>          Components: client
>            Reporter: Tsz-wo Sze
>            Assignee: Tsz-wo Sze
>            Priority: Major
>             Fix For: 1.1.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The leader information can be specified when building a RaftClient.  If the leader information is missing, the RaftClient will make a guess and use one of the highest priority servers as the initial leader.
> The JIRA proposes to have a leader cache to record the leader information for each group.  Then a new RaftClient can use the leader information from the cache so that it don't have to guess who is the leader.
> A use case is Ozone S3 which creates multiple RaftClient(s) connecting to the same Raft group.  When the guessed leader is incorrect, all the new clients have to do a retry.  Thanks [~kerneltime] for finding out this problem!



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