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

Investigate ShardRegistry reload on config server during removeShard

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.3
    • 4.3.2
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2019-12-02, Sharding 2019-12-16, Sharding 2019-12-30

    Description

      Currently, ShardRegistry gets reloaded in the config server while running removeShard:

      https://github.com/mongodb/mongo/blob/ec9a2f13d82f141d8aca9e3df9e9112b722f2563/src/mongo/db/s/config/sharding_catalog_manager_shard_operations.cpp#L810
      https://github.com/mongodb/mongo/blob/ec9a2f13d82f141d8aca9e3df9e9112b722f2563/src/mongo/db/s/config/sharding_catalog_manager_shard_operations.cpp#L852

      However, the reload is done with read concern majority so it might not see the changes that were applied during the removeShard command. Investigate whether if reload is even needed in the config server and if yes, how to fix it.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: