Description
Starting new peers with empty conf when membership changes can cause infinity election.
Supposing we want to replace 2 peers from a 3 peers cluster. Normally we start the 2 new peers with empty conf. This can cause an infinity election and make the cluster unavailable forever.
I will upload a patch to describe the case. And I will upload a document to describe the current dilemma when performing membership changes.
TestMembership simulates the 'replacing 2 peers from a 3 peers cluster' issue. It ends with an infinity leader election. (https://github.com/apache/ratis/pull/943/files)
Attachments
Attachments
Issue Links
- is related to
-
RATIS-1930 Add a conf for enable/disable majority-add.
- Resolved
- relates to
-
RATIS-1911 Create a simple example to demonstrate how to perform ratis cluster membership changes.
- Resolved
- links to