Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2022-10-17, Execution Team 2022-10-31
Linked BF Score:
140

Currently for checkpointing we use ResourceLock with a manually constructed ResourceId each time. This is incorrect usage as it doesn't go through the ResourceIdFactory. We should instead use ResourceMutex with ExclusiveLock and SharedLock.

is depended on by

SERVER-70467 Prevent manually using RESOURCE_MUTEX

Closed

is duplicated by

SERVER-70536 Invalid construction of "checkpoint" ResourceId outside ResourceIdFactory

Closed

is related to

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

Closed

SERVER-70322 BalancerStatsRegistry inappropriately constructs ResourceId outside ResourceIdFactory

Closed

related to

SERVER-69247 Add concurrency control for taking checkpoints

Closed

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

Closed

(1 related to)

Assignee:: Gregory Noma

Reporter:: Gregory Noma

Participants:: Githook User, Gregory Noma

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: Oct 11 2022 01:39:14 AM UTC

Updated:: Oct 29 2023 09:32:05 PM UTC

Resolved:: Oct 14 2022 02:11:25 PM UTC