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

updateReplicaSetOnConfigServer should not skip config server

    XMLWordPrintableJSON

Details

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

    Description

      When a shard's configuration changes, each mongos will detect this and then update the corresponding config.shards document in the config server. Currently, this logic skips the update if the replica set that changed was the config server, but now the config server can be a shard, so we should not skip this step.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: