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

Remove globalInShutdownDeprecated from the condition to cleanly terminate migrations

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • 3.7.9
    • Sharding
    • None
    • Sharding
    • ALL
    • 0

    Description

      Note that the condition here:

      https://github.com/mongodb/mongo/blob/r3.7.9/src/mongo/db/s/migration_source_manager.cpp#L483

      Checks for the shutdown status and calls inShutdown(). Because inShutdown is using memory_order_relaxed, it is totally legal for another thread to be in "shutdown" state and return a shutdown error, while the migration thread still sees that it is not yet in "shutdown".

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: