[SERVER-50913] Teardown config server last in sharded cluster Created: 14/Sep/20  Updated: 29/Oct/23  Resolved: 15/Sep/20

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

Type: Improvement Priority: Major - P3
Reporter: Mikhail Shchatko Assignee: Mikhail Shchatko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-31173 Change resmoke sharded cluster shutdo... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: STM 2020-09-21
Participants:
Story Points: 0.5

 Description   

Members of sharded cluster should be teared down in the following order:
Mongos routers -> Each shard replica sets -> Config servers

It will reduce the noise in the logs and decrease overall shutdown time.



 Comments   
Comment by Githook User [ 16/Sep/20 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com'}

Message: SERVER-50913 Teardown config server last in sharded cluster

(cherry picked from commit 7c412fa8b639239bce5d51d0634b31efa26b91f7)
Branch: v4.4
https://github.com/mongodb/mongo/commit/8d96f60771ae00ef565b4bc5eee28882f6f9ad59

Comment by Githook User [ 15/Sep/20 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com'}

Message: SERVER-50913 Teardown config server last in sharded cluster
Branch: master
https://github.com/mongodb/mongo/commit/d466559ae68fb38015921321aab9297dcc35fa1a

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