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

Tsz Wo Nicholas Sze commented on RATIS-100:
-------------------------------------------

> 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. ...

Yes, the setConf entry cannot get committed.  However, the old nodes still will 
keep retrying leader election with the new nodes.

Here is the dead lock:
- Old nodes: retrying leader election to get a majority from old + new nodes.
- New nodes: stating in STARTING state and refuse to vote.

It seems that the new nodes should vote even if it is in STARTING state.  Would 
it work?

> 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, r100_20170809.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