[ 
https://issues.apache.org/jira/browse/RATIS-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119302#comment-16119302
 ] 

Jing Zhao commented on RATIS-100:
---------------------------------

bq. One or more node may start a leader election. However, there could be many 
new nodes still in STARTING state and refuse to vote. Then, no new leader can 
be elected.

If more than a quorum of nodes in the new conf are in the STARTING state and do 
not join normal protocol, then the (old, new) conf entry cannot get committed. 
In that case, the leader election will still depend on the old configuration. 
Is it possible that no new leader can be elected is because we are using 
{{reinitialize}} API for old peers? For these peers we should call 
{{setConfiguration}} instead of {{reinitialize}}.

> Test multiple raft groups with a state machine
> ----------------------------------------------
>
>                 Key: RATIS-100
>                 URL: https://issues.apache.org/jira/browse/RATIS-100
>             Project: Ratis
>          Issue Type: Test
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>         Attachments: r100_20170804.patch
>
>
> We propose to add a test similar to 
> ReinitializationBaseTest.runTestReinitializeMultiGroups(..) with a state 
> machine so that it can test if the states are recorded correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to