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

MigrationSourceManager::done called twice

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.2.0-rc1
    • Affects Version/s: 3.1.9
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding B (10/30/15)

      One is in the destructor of the statusHolder:

      https://github.com/mongodb/mongo/blob/r3.1.9/src/mongo/db/s/move_chunk_command.cpp#L83

      and the other is when the critical section finishes:

      https://github.com/mongodb/mongo/blob/r3.1.9/src/mongo/db/s/move_chunk_command.cpp#L511

      This creates a small window where a new migration can start and the destructor will set the state of the migration to not active.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: