[SERVER-63542] Investigate the difference in startup sequence in Config and shard servers Created: 10/Feb/22  Updated: 29/Oct/23  Resolved: 21/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Andrew Witten (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2022-03-07, Sharding NYC 2022-03-21
Participants:
Story Points: 5

 Description   

In particular, initializeGlobalShardingStateForMongoD() and setShardingInitialized() methods are invoked sooner at Config server, essentially making it to step in its role before other steps an ordinary shard will wait for.


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