Xinyu Tan created RATIS-2060:
--------------------------------
Summary: Avoid unexpected shutdown of RaftServerProxy during
membership change
Key: RATIS-2060
URL: https://issues.apache.org/jira/browse/RATIS-2060
Project: Ratis
Issue Type: Improvement
Reporter: Xinyu Tan
Assignee: Xinyu Tan
Attachments: image-2024-04-24-11-11-41-950.png,
image-2024-04-24-11-11-52-374.png
When IoTDB migrates shards, for A RaftGroup, if it wants to change from [A,B,C]
to [B,C,D], it will first change it to [A,B,C,D] and then change it to [B,C,D].
After changing the member list to [B,C,D], Node A may vote again and get
NOT_IN_CONF reply, in which case it will shut down the entire RaftServerProxy,
which will affect the normal behavior of other RaftGroups.
The expectation at this point is to simply close the current RaftServerImpl and
not the RaftServerProxy.
!image-2024-04-24-11-11-52-374.png!
[~szetszwo] What's your opinion?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
