[
https://issues.apache.org/jira/browse/RATIS-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz-wo Sze updated RATIS-1594:
------------------------------
Fix Version/s: 3.0.0
2.3.1
> Support ADD mode to SetConfiguration
> ------------------------------------
>
> Key: RATIS-1594
> URL: https://issues.apache.org/jira/browse/RATIS-1594
> Project: Ratis
> Issue Type: Sub-task
> Components: server
> Reporter: Yaolong Liu
> Assignee: Yaolong Liu
> Priority: Major
> Fix For: 3.0.0, 2.3.1
>
> Attachments: 658_review.patch
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> Support ADD mode to setConfiguration: we only add members to the new member
> list that are temporarily not in the current list, and do not delete existing
> members.
> Suppose there are now three members A B C in the cluster,
> D called setConfiguration(newPeers=[A, B, C, D])
> E called setConfiguration(newPeers=[A, B, C, E])
> In the current code logic, the cluster members will end up being A, B, C, D
> or A, B, C, E.
> In ADD mode:
> We assume that E's request is executed successfully first, and the current
> members of the cluster are A, B, C, E, and then start to execute D's request.
> At this time, we find that D is not in the list, so we just add D instead of
> deleting E. The clusters eventually become A, B, C, D, E
> In addition, we can hand over to the user whether to use concurrent mode to
> execute setConfiguration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
