-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Storage
-
Sharding EMEA
-
Fully Compatible
-
Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10
-
156
The OperationContextNoop was introduced long time ago as means to abstract lock acquisitions and access to the recovery unit for unit-tests (and MongoS). With the unit-testing tools that we have now, such as ServiceContextTest, this seems to no longer be necessary, so we should try to get rid of it.
The most usages seem to be in the Execution Team's test code, so I am assigning this ticket to their backlog.
- is depended on by
-
SERVER-77213 Move the all transactions-related state from OperationContext to TransactionResources
- Blocked
- related to
-
SERVER-42901 Use LockerImpl for the startup code path instead of LockerNoop
- Closed