Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 7.1.0-rc0
Affects Version/s: None
Component/s: Concurrency, Internal Code
Labels:
- nyc
- techdebt

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Linked BF Score:
166
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

(1 is related to, 1 related to)

Assignee:: Kaloian Manassiev
Reporter:: Mathias Stearn
Participants:: Githook User, Ian Whalen, Kaloian Manassiev, Mathias Stearn
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Nov 02 2016 04:52:18 PM UTC
Updated:: Jul 20 2023 07:20:23 PM UTC
Resolved:: Jul 06 2023 03:13:42 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates