[SERVER-45007] PBWM acquisition in GlobalLock constructor ignores deadline Created: 06/Dec/19  Updated: 29/Oct/23  Resolved: 10/Feb/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.2.4, 4.3.4

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-43339 PBWM locks acquired part of GlobalLoc... Closed
is related to SERVER-44821 retrieving storage stats for currentO... Closed
is related to SERVER-45006 LockerImpl::wasGlobalLockTaken() alwa... Closed
is related to SERVER-38341 Remove Parallel Batch Writer Mutex Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2020-02-10, Execution Team 2020-02-24
Participants:
Linked BF Score: 14

 Description   

This PBWM lock acquisition ignores the passed in deadline. A consequence is that this GlobalLock construction can hang waiting for the PBWM lock.



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

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-45007 PBWM lock acquisition in GlobalLock supports deadline

(cherry picked from commit 73acb91e3989754ffa0ea98dc908362cad76c1ef)
Branch: v4.2
https://github.com/mongodb/mongo/commit/7d6f64a440076a8ff644188eb4d069a5ec7d490b

Comment by Githook User [ 19/Feb/20 ]

Author:

{'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}

Message: SERVER-45007 ResourceLock::lock() supports deadline

(cherry picked from commit 0f502c28c373d03088150f478b243d88e1decb26)
Branch: v4.2
https://github.com/mongodb/mongo/commit/2aee65d949e6e93f0142d70d7dcdc3833258e9fb

Comment by Githook User [ 19/Feb/20 ]

Author:

{'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}

Message: SERVER-45007 ResourceLock::lock() always requires OperationContext

(cherry picked from commit 25ffb326e1ecd57db0e1c309d0bcf6b8fd2e072c)
Branch: v4.2
https://github.com/mongodb/mongo/commit/48373e410074700117285938ab2b6d9baa6c06a5

Comment by Githook User [ 10/Feb/20 ]

Author:

{'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}

Message: SERVER-45007 PBWM lock acquisition in GlobalLock supports deadline
Branch: master
https://github.com/mongodb/mongo/commit/73acb91e3989754ffa0ea98dc908362cad76c1ef

Comment by Githook User [ 10/Feb/20 ]

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-45007 ResourceLock::lock() supports deadline
Branch: master
https://github.com/mongodb/mongo/commit/0f502c28c373d03088150f478b243d88e1decb26

Comment by Githook User [ 10/Feb/20 ]

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-45007 ResourceLock::lock() always requires OperationContext
Branch: master
https://github.com/mongodb/mongo/commit/25ffb326e1ecd57db0e1c309d0bcf6b8fd2e072c

Comment by Benety Goh [ 11/Dec/19 ]

The CI failure that motivated this ticket can also be addressed by SERVER-44821, which is already in progress.

The PBWM will eventually be removed in SERVER-38341.

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