[SERVER-43339] PBWM locks acquired part of GlobalLock::GlobalLock() should be interruptible. Else, it won't respect MaxTimeMS. Created: 13/Sep/19  Updated: 29/Oct/23  Resolved: 30/Sep/19

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.4

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-45007 PBWM acquisition in GlobalLock constr... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2019-10-07
Participants:

 Description   

Currently, we are not passing opCtx for pbwm lock acquisition. As a result, it's not interruptible and won't respect maxTimeMS.



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

Author:

{'name': 'Xiangyu Yao', 'username': 'xy24', 'email': 'xiangyu.yao@mongodb.com'}

Message: SERVER-43339 Make PBWM respect MaxTimeMS

This only affects the PBWM taken by the Global lock. The PBWM taken by
secondary batch application is still uninterruptible.

(cherry picked from commit 711d26d8a5c5d64b26dd7dd8d66d489a4918e79f)

create mode 100644 jstests/noPassthrough/pbwm_max_time_ms.js
Branch: v4.2
https://github.com/mongodb/mongo/commit/ad0f72c1e5c452d7869fd829736179092b7ab88f

Comment by Githook User [ 30/Sep/19 ]

Author:

{'username': 'xy24', 'email': 'xiangyu.yao@mongodb.com', 'name': 'Xiangyu Yao'}

Message: SERVER-43339 Make PBWM respect MaxTimeMS

This only affects the PBWM taken by the Global lock. The PBWM taken by
secondary batch application is still uninterruptible.
Branch: master
https://github.com/mongodb/mongo/commit/711d26d8a5c5d64b26dd7dd8d66d489a4918e79f

Generated at Thu Feb 08 05:02:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.