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

Posted to issues@ratis.apache.org by "Lokesh Jain (JIRA)" <ji...@apache.org> on 2018/01/24 15:44:00 UTC

[jira] [Updated] (RATIS-201) MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

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

Lokesh Jain updated RATIS-201:
------------------------------
    Description: It can be possible for more than one server to have their role set as LEADER in a ratis ring. There can be a race condition where term of a follower is updated but its role is not yet updated to FOLLOWER. In such a scenario MiniRaftCluster#getLeader would throw IllegalStateException.  (was: It can be possible for more than one server to have their role set as LEADER in a ratis ring. One of the servers would actually be a leader and the rest may be LEADER from previous terms. In such a scenario MiniRaftCluster#getLeader would throw IllegalStateException.)

> MiniRaftCluster#getLeader may incorrectly throw IllegalStateException
> ---------------------------------------------------------------------
>
>                 Key: RATIS-201
>                 URL: https://issues.apache.org/jira/browse/RATIS-201
>             Project: Ratis
>          Issue Type: Bug
>            Reporter: Lokesh Jain
>            Assignee: Lokesh Jain
>            Priority: Major
>
> It can be possible for more than one server to have their role set as LEADER in a ratis ring. There can be a race condition where term of a follower is updated but its role is not yet updated to FOLLOWER. In such a scenario MiniRaftCluster#getLeader would throw IllegalStateException.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)