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

Posted to issues@ratis.apache.org by "Shashikant Banerjee (JIRA)" <ji...@apache.org> on 2019/07/19 10:17:00 UTC

[jira] [Created] (RATIS-627) Rpc timeouts and leader election timeout configs are misleading

Shashikant Banerjee created RATIS-627:
-----------------------------------------

             Summary: Rpc timeouts and leader election timeout configs are misleading
                 Key: RATIS-627
                 URL: https://issues.apache.org/jira/browse/RATIS-627
             Project: Ratis
          Issue Type: Bug
          Components: server
    Affects Versions: 0.4.0
            Reporter: Shashikant Banerjee
             Fix For: 0.4.0


Currently, for a leader election to complete, timeouts are decided by min and max values given by rpc.timeout.min and rpc.timeout.max. But, there is a separate config for leader timeout given by "leader.election.timeout" after which the statemachine of the server is notified
about leader election pending for a long time. The naming of the configs seem confusing at times.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)