-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Concurrency, Internal Code
-
Storage Execution
-
Fully Compatible
-
166
Now that the real LockManager and LockState are usable in unittests we should remove the fake LockerNoop. This is related to the work to merge OperationContext/Impl/Noop into a single concrete type.
- causes
-
SERVER-79047 [BM test] Collection lock not acquired on sharding_write_router_bm test
- Closed
- depends on
-
SERVER-42901 Use LockerImpl for the startup code path instead of LockerNoop
- Closed
-
SERVER-60229 lock manager for mongos
- Closed
- is depended on by
-
SERVER-77213 Move the all transactions-related state from OperationContext to TransactionResources
- Blocked
- is related to
-
SERVER-35970 Use regular Locker during storage engine initialization
- Closed
-
SERVER-31247 enhance LockerNoOp
- Closed
- related to
-
SERVER-78744 Access Locker through locker_api.h
- Closed