[SERVER-68584] Generalize skipTicketAcquisitionForLock for low and high priority operations Created: 05/Aug/22  Updated: 29/Oct/23  Resolved: 07/Sep/22

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Leonardo Menti (Inactive)
Resolution: Fixed Votes: 0
Labels: PM-2935-Milestone1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19
Participants:

 Description   

new description
(1) Generalize SkipTicketAcquisitionForLock to handle setting operation priority to low priority as well as high priority. 

(2) Rename Locker::skipAcquireTicket() with a more appropriate name involving setting the priority to kHigh. 

Preserve the existing functionality of both methods, but give them new names and generalize the RAII type for other operation priorities

 

old description

Currently, operations can opt out of ticket acquisition via Locker::skipAcquireTicket() and SkipTicketAcquisitionForLock

(1) Investigate the difference between the two opt-out methods: is there an impact on specifying when we acquire the GlobalLock the priority versus having a scope guard to skip ticket acquisition?

(2) Ensure all operations that currently opt out continue to opt out

(3) Maintain legacy behavior that tickets who are high priority skip ticket acquisition, regardless of whether the feature is enabled



 Comments   
Comment by Githook User [ 07/Sep/22 ]

Author:

{'name': 'Leonardo Menti', 'email': 'leonardo.menti@mongodb.com', 'username': 'leonardomenti'}

Message: SERVER-68584 Generalize skipTicketAcquisitionForLock
Branch: master
https://github.com/mongodb/mongo/commit/cd8f093c066e3a7a236857214eef50c61c8c47a5

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