[SERVER-41240] LockerImpl::getFlowControlTicket should check for uninterruptible locks Created: 20/May/19  Updated: 29/Oct/23  Resolved: 20/May/19

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: None
Fix Version/s: 4.1.12

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2019-05-20
Participants:
Linked BF Score: 0

 Description   

Testing of Flow Control found that a primary can crash on an InterruptedDueToStepdown DBException when an UninterruptibleLockGuard is in use on a lock acquisition that is gated by Flow Control. Lock acquisitions that are gated by UninterruptibleLockGuards should not be subject to Flow Control. There are very few such acquisitions and all of them are by system operations so this work should be safe to do.



 Comments   
Comment by Githook User [ 20/May/19 ]

Author:

{'email': 'maria@mongodb.com', 'name': 'Maria van Keulen', 'username': 'mvankeulen94'}

Message: SERVER-41240 Do not Flow Control uninterruptible lock acquisitions.
Branch: master
https://github.com/mongodb/mongo/commit/24760ca934a3c7843731de117839070ddf7fd3cc

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