Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-69692

Implement the startup sequence for the catalog shard

    • Type: Icon: New Feature New Feature
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding NYC
    • 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
    • 1

      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.

            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            0 Vote for this issue
            1 Start watching this issue