[SERVER-44807] Allow transition from RS_STARTUP to RS_REMOVED directly Created: 22/Nov/19  Updated: 27/Oct/23  Resolved: 25/Feb/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-15740 a node newly added to a replset somet... Closed
Assigned Teams:
Replication
Participants:

 Description   

If a node is not included in the latest config, when it tries to join the replset, the node will get the new config that doesn't have itself. SERVER-15740 disallow the transition from RS_STARTUP to RS_REMOVED directly due to the implementation of checkQuorumForConfigChange. With Safe Reconfig project, checkQuorumForConfigChange won't talk to the nodes in the new config before installing it, so this won't be a problem.



 Comments   
Comment by Siyuan Zhou [ 25/Feb/20 ]

Since we will keep the quorum check for reconfig, the old behavior reminds the same. Closing as Works as Designed.

Generated at Thu Feb 08 05:07:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.