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

Mark MigrationDestinationManager::_migrateThread killable for stepdown

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • ALL

      MigrationDestinationManager::_migrateThread() is not marked killable. We should probably do something like what we did for the range deleter to call setSystemOperationKillable() on the client thread. Otherwise, the migrateThread could be blocked on a prepared transaction for a collection lock (held by a prepared transaction) while holding onto the RSTL, preventing state transition from proceeding. Calling setSystemOperationKillable() will allow stepDown to kill the migrateThread operation.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: