-
Type: Improvement
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Execution Team 2021-11-15, Execution Team 2022-01-24
mongos currently runs without a full featured resource lock manager. OperationContext instances are created with LockerNoop for the lock implementation, which has sometimes led to issues such as those described in SERVER-59591.
This ticket looks into whether it makes sense to install a lock manager for mongos with a lock implementation closer to that in LockerImpl.
- is depended on by
-
SERVER-26879 Get rid of LockerNoop
- Closed
- is related to
-
SERVER-59591 LockerNoop::isW() always returns true allowing multiple operations think they are holding the global exclusive lock at the same time
- Closed
-
SERVER-42901 Use LockerImpl for the startup code path instead of LockerNoop
- Closed
-
SERVER-59618 Avoid using LockerNoop outside of unit tests
- Closed
-
SERVER-77353 Get rid of the Locker implementation for MongoS
- Closed
- related to
-
SERVER-77613 Complete TODO listed in SERVER-60229
- Closed