Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- or-workload-management
- techdebt

Assigned Teams:

Storage Execution
Sprint:
Execution Team 2022-11-14, Execution Team 2022-12-12, Execution Team 2022-11-28
Confidence Status:
None
Work Order:
3

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

Uses of UninterruptibleLockGuard indicate places in the code that do not comply with MongoDB's requirement that all operations be interruptible at places where they block to wait for resources. Every one of them is a potential future deadlock, and adds complexity to other parts of the codebase. We should reimplement codepaths that depend on UninterruptibleLockGuard so as to be interruptible.

depends on

SERVER-71610 [StorEx] Remove or document instances of UninterruptibleLockGuard

Closed

SERVER-90803 Remove the use of UninterruptibleLockGuard in transaction participant

Open

SERVER-91733 Remove the use of UninterruptibleLockGuard in ReplicationCoordinatorExternalState

Open

SERVER-90799 Remove the usage of UninterruptibleLockGuard in the IndexBuildsCoordinator

Backlog

SERVER-90800 Remove the usage of UninterruptibleLockGuard in MultiIndexBlock

Blocked

SERVER-68874 Consider making waitAfterPinningCursorBeforeGetMoreBatch only hang instead of also fiddling with locks (while-loop taking and releasing locks)

Closed

SERVER-90798 Replace CollectionShardingRuntime and DatabaseShardingState use of interruptible ResourceMutex

Closed

SERVER-90801 Remove the usage of UninterruptibleLockGuard dropDatabase

Closed

SERVER-90802 Remove the use of UninterruptibleLockGuard in OplogBatcher, ReplicationCoordinator, and ReplicationCoordinatorExternalState

Closed

SERVER-71444 [Sharding] Remove or document instances of UninterruptibleLockGuard

Open

SERVER-68867 Use linter to prevent new instances of UninteruptibleLockGuard

Closed

SERVER-71441 [Query] Remove or document instances of UninterruptibleLockGuard

Closed

SERVER-71443 [Replication] Remove or document instances of UninterruptibleLockGuard

Closed

is depended on by

SERVER-90804 Remove UninterruptibleLockGuard and InterruptibleLockGuard

Closed

related to

SERVER-69506 An InterruptibleLockGuard should be placed in the PlanExecutorSBE class as a private member if the use cases are expanded beyond the find/agg/getMore commands while the UninterruptibleLockGuard still exists

Backlog

SERVER-68867 Use linter to prevent new instances of UninteruptibleLockGuard

Closed

(8 depends on, 1 is depended on by, 2 related to)

Assignee:: [DO NOT USE] Backlog - Storage Execution Team
Reporter:: Andy Schwerin
Participants:: [DO NOT USE] Backlog - Storage Execution Team, Andy Schwerin, Dianna Hohensee, Gregory Noma, Kaloian Manassiev
Votes:: 1 Vote for this issue
Watchers:: 13 Start watching this issue

Created:: Aug 16 2022 06:10:37 PM UTC
Updated:: Mar 12 2025 05:57:05 PM UTC
Confidence Status Last Update:: 11/Nov/22 10:20 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates