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

Attempting to add the config server as a shard shouldn't remove its RSM

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Sharding NYC
    • Fully Compatible
    • ALL
    • Sharding NYC 2023-03-06

    Description

      As of SERVER-73685 the way to make the config server a catalog shard is to run the transitionToCatalogShard command. A user can still attempt to add the config server as a shard via addShard, which is correctly rejected, but will trigger removing the ReplicaSetMonitor for the config server via this scope guard, which should not happen because the config server still needs to be able to target itself.

      We should also investigate if addShard/transitionToCatalogShard is creating a new RSM for the config server when it creates a Shard object here. The config server will always already have an RSM for itself, so this would be unnecessary.

      Attachments

        Activity

          People

            wenqin.ye@mongodb.com Wenqin Ye
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: