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 Nicholas Sze (JIRA)" <ji...@apache.org> on 2018/02/05 21:12:00 UTC

[jira] [Updated] (RATIS-201) RaftBasicTests.testWithLoad should use RaftTestUtil.waitForLeader instead of cluster.getLeader()

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

Tsz Wo Nicholas Sze updated RATIS-201:
--------------------------------------
    Priority: Minor  (was: Major)
     Summary: RaftBasicTests.testWithLoad should use RaftTestUtil.waitForLeader instead of cluster.getLeader()  (was: MiniRaftCluster#getLeader may incorrectly throw IllegalStateException)

> RaftBasicTests.testWithLoad should use RaftTestUtil.waitForLeader instead of cluster.getLeader()
> ------------------------------------------------------------------------------------------------
>
>                 Key: RATIS-201
>                 URL: https://issues.apache.org/jira/browse/RATIS-201
>             Project: Ratis
>          Issue Type: Bug
>            Reporter: Lokesh Jain
>            Assignee: Lokesh Jain
>            Priority: Minor
>         Attachments: RATIS-201.001.patch, RATIS-201.002.patch, RATIS-201.003.patch
>
>
> 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)