[SERVER-26280] MigrationManager expects ReplSetDistLockManager::tryLockWithLocalWriteConcern to return LockStateChangeFailed, which it never does Created: 23/Sep/16  Updated: 19/Nov/16  Resolved: 23/Sep/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.15

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2016-10-10
Participants:

 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.



 Comments   
Comment by Githook User [ 23/Sep/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-26280 change ErrorCode expectation in MigrationManager
Branch: master
https://github.com/mongodb/mongo/commit/aad3bcd6d14152459ff362f69b2e20ebbd68b053

Generated at Thu Feb 08 04:11:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.