Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2023-01-23
Confidence Status:
None
Work Order:
3

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

RESOURCE_MUTEX should not be used manually when constructing a ResourceId. Instead, ResourceMutex should be used which goes through the ResourceIdFactory. We should enforce this to prevent misuses.

depends on

SERVER-70154 DatabaseShardingState inappropriately constructs a RESOURCE_MUTEX ResourceId, leading to uncaught exception

Closed

SERVER-70322 BalancerStatsRegistry inappropriately constructs ResourceId outside ResourceIdFactory

Closed

SERVER-70431 Checkpointing manually constructs ResourceId using RESOURCE_MUTEX

Closed

is related to

SERVER-74938 POC PM-2850

Closed

related to

SERVER-69893 Add the ability to acquire lock manager mutex resources by name

Closed

Assignee:: Daniel Gomez Ferro
Reporter:: Gregory Noma
Participants:: Daniel Gomez Ferro, Githook User, Gregory Noma
Votes:: 1 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Oct 11 2022 03:28:35 PM UTC
Updated:: Oct 29 2023 09:32:03 PM UTC
Resolved:: Jan 16 2023 02:12:05 PM UTC
Confidence Status Last Update:: 09/Jan/23 3:56 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates