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

Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2021/08/12 03:27:00 UTC

[jira] [Created] (RATIS-1392) Cache leader information in RaftClient

Tsz-wo Sze created RATIS-1392:
---------------------------------

             Summary: Cache leader information in RaftClient
                 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


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)