[SERVER-74570] Parallel replica set shutdown does not use extended ReplSetTest object from continuous stepdown suite Created: 02/Mar/23  Updated: 28/Nov/23

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

Type: Bug Priority: Major - P3
Reporter: Wenqin Ye Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Cluster Scalability
Operating System: ALL
Sprint: Sharding NYC 2023-05-15, Sharding NYC 2023-05-29, Sharding NYC 2023-06-12, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27
Participants:
Story Points: 1

 Description   

The new thread that is created to stop a replica set during parallel shutdown does not use the extended ReplSetTest object from the continuous config step-down suite. 

This causes an error in the test because when the new thread calls `stopSet()` on the `ReplSetTest` object it does not use the extended `stopSet()` which is responsible for stopping the continuous config step down thread. 

The potential solution could be just to not allow parallel shutdowns when running the continuous config stepdown suite.



 Comments   
Comment by Wenqin Ye [ 07/Apr/23 ]

For some added context, this causes any test with catalog shard enabled to fail on the continuous config stepdown suite. The failure is purely a test failure that indicates that the continuous config stepdown suite's thread did not exit properly.

This test error does not show up for tests that don't have catalog shard enabled because as part of stopping a `ShardTest`, the js testing framework will also stop the config server replica set which does use the extended `stopSet` which stops the continuous config step down thread. But in catalog shard mode, the config server is also a shard and so the code to stop the config server is never called.

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