[SERVER-69692] Implement the startup sequence for the catalog shard Created: 14/Sep/22  Updated: 27/Oct/23  Resolved: 21/Feb/23

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

Type: New Feature Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Gone away Votes: 0
Labels: sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-69607 Test infrastructure to support catalo... Closed
Assigned Teams:
Sharding NYC
Sprint: Sharding 2022-10-03, Sharding 2022-10-17, Sharding NYC 2022-10-31, Sharding NYC 2022-11-14, Sharding NYC 2022-11-28, Sharding 2022-12-12, Sharding NYC 2022-12-26, Sharding NYC 2023-01-09, Sharding NYC 2023-01-23, Sharding NYC 2023-02-06, Sharding NYC 2023-02-20, Sharding NYC 2023-03-06
Participants:
Story Points: 1

 Description   

In src/mongo/db/mongod_main.cpp the startup sequences should handle the catalog shard properly.

The new functionality expected after this change:
1. Necessary primary only services will be registered and started
2. Necessary set of op observers is registered

This must be done after SERVER-69607 to enable proper testing. The integration test remains the same - the catalog shard should respond to Hello request with catalogShard and configsvr options set. At this point it will not be possible to start the ShardingTest properly, it will not complete. The test will start a standalone mongod, unless it will turn out to be impossible.


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