[
https://issues.apache.org/jira/browse/RATIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354102#comment-16354102
]
Lokesh Jain commented on RATIS-201:
-----------------------------------
[~szetszwo] Yes that should also work. In case of exception one leader change
operation would be skipped though. I have added a patch with the corresponding
change.
> 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
> Fix For: 0.2.0-alpha
>
> Attachments: RATIS-201.001.patch, RATIS-201.002.patch,
> RATIS-201.003.patch, RATIS-201.004.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)
