[RATIS-2060] Avoid unexpected shutdown of RaftServerProxy during membership change

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.0
• Assignee: Xinyu Tan
• Reporter: Xinyu Tan
• Created: 24/Apr/24 03:18
• Updated: 25/Apr/24 11:45
• Resolved: 25/Apr/24 11:45

Description

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.

szetszwo What's your opinion?

Issue Links

• links to: GitHub Pull Request #1069