[SERVER-31173] Change resmoke sharded cluster shutdown order Created: 19/Sep/17  Updated: 02/Mar/21  Resolved: 22/Feb/21

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

Type: Improvement Priority: Major - P3
Reporter: Ian Boros Assignee: Mikhail Shchatko
Resolution: Duplicate Votes: 0
Labels: stm, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-50913 Teardown config server last in sharde... Closed
Related
is related to SERVER-30979 Run the fuzzer with CSRS primary step... Closed
Sprint: STM 2021-03-08
Participants:
Story Points: 0

 Description   

Currently, the order members of a sharded cluster are shutdown in is:
1) Config Servers
2) Mongos
3) Shard members

See https://github.com/mongodb/mongo/blob/master/buildscripts/resmokelib/testing/fixtures/shardedcluster.py#L148-L171

If we change the shutdown order to be what's below, the we can shave ~1 minute off the shutdown time in some configurations.
1) Mongos
2) Shard members
3) Config Servers

We think this is because the shard members may try to contact the config servers after they've been shutdown which could lead to the shard members entering retry loop.


Generated at Thu Feb 08 04:26:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.