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

Consistently handle admin database like config database in sharding

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Sharding NYC
    • Fully Compatible
    • Sharding NYC 2023-02-06, Sharding NYC 2023-02-20, Sharding NYC 2023-04-03

    Description

      The config database is treated specially in sharding because it is assumed to be owned by the config server and uses the hardcoded "fixed" database version. To handle this, we have logic that's skipped for the config db, e.g. asserting when asserting a ShardingDDLCoordinator is running on the primary shard for its namespace. Often we only special case the config db, but in theory the admin db should be handled the same way.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: