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

MigrationManager expects ReplSetDistLockManager::tryLockWithLocalWriteConcern to return LockStateChangeFailed, which it never does

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.3.15
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2016-10-10

    Description

      ReplSetDistLockManager::tryLockWithLocalWriteConcern won't return LockStateChangeFailed: it specifically accounts for it and returns LockBusy instead.

      However, the MigrationManager, currently the sole user of the function, expects that error code because here. Instead of LockStateChangeFailed, MigrationManager should check for LockBusy.

      If there is any 3.2 shard with an active migration, the MigrationManager will abandon all migration recoveries, not just the 3.2 migration.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee
            dianna.hohensee@mongodb.com Dianna Hohensee
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: