[SERVER-70431] Checkpointing manually constructs ResourceId using RESOURCE_MUTEX Created: 11/Oct/22  Updated: 29/Oct/23  Resolved: 14/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-70467 Prevent manually using RESOURCE_MUTEX Closed
Duplicate
is duplicated by SERVER-70536 Invalid construction of "checkpoint" ... Closed
Related
related to SERVER-69247 Add concurrency control for taking ch... Closed
related to SERVER-69893 Add the ability to acquire lock manag... Closed
is related to SERVER-70154 DatabaseShardingState inappropriately... Closed
is related to SERVER-70322 BalancerStatsRegistry inappropriately... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-10-17, Execution Team 2022-10-31
Participants:
Linked BF Score: 140

 Description   

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.



 Comments   
Comment by Githook User [ 14/Oct/22 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-70431 Use `ResourceMutex` for checkpointing
Branch: master
https://github.com/mongodb/mongo/commit/a81af278bf063f677c6b23ae4c50c537edf7b07a

Generated at Thu Feb 08 06:16:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.