[SERVER-68768] Collection validation should be skipped when shutting down recipient nodes removed from a replica set Created: 11/Aug/22  Updated: 29/Oct/23  Resolved: 23/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0, 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Sophia Tan Assignee: Sophia Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Server Serverless 2022-08-22, Server Serverless 2022-09-05
Participants:
Linked BF Score: 20

 Description   

In serverless js test shard_split_concurrent_reconfig.js, we remove recipient nodes from donor replica set with reconfig command and then we shut down recipient nodes. During shutting down these nodes, the collection validation will throw an exception if the node status is changed from SECONDARY to REMOVED after passing no primary or secondary check.

We should skip the collection validation in this case. 



 Comments   
Comment by Steven Vannelli [ 15/Aug/22 ]

Scheduling this for this upcoming Friday.

Generated at Thu Feb 08 06:11:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.