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

setAllowMigrationsAndBumpOneChunk should send the refresh to all shards

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • v7.0, v6.3
    • Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06
    • 139

    Description

      If a migration of the last chunk on a shard commits right before we stop migrations in the catalog manager, the refresh will not be sent to that shard (which is a donor of the migration). This means that we do not wait for the critical section on the donor shard, which can cause the ddl which called stopMigrations to continue when it should wait for the migration to complete.

      Instead of sending the refresh to the shards that own chunks for the migration, we should send it to all shards.

      Attachments

        Activity

          People

            allison.easton@mongodb.com Allison Easton
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: