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

Shard is shutting down before finishing draining in test

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v5.3, v5.0
    • Sharding EMEA 2022-04-18
    • 18

    Description

      auth_add_shard.js is relying on removeShard to wait until the removed shard is fully drained before shutting down, however, remove shard works at the config server level, and it only checks if the shard has no chunks, so we might end up in a situation where the last migration just committed to the config server, but before cleaning up, which includes starting the source shard range deletion, removing the destination shard range deletion document and removing the migration coordinator document.

      We should wait not only for the removeShard to be successful, but also to ensure there is no migration coordinator document on the donor shard, meaning, the last migration has successfully transfer the latest chunk to the destination shard, and all cleanup processes are finished.

      Attachments

        Activity

          People

            allison.easton@mongodb.com Allison Easton
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: