[SERVER-58219] Investigate ViewCatalog::reload() lock acquisition Created: 02/Jul/21  Updated: 16/Aug/21  Resolved: 16/Aug/21

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

Type: Task Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Dan Larkin-York
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-48129 Invariant that operations which are h... Closed
Sprint: Execution Team 2021-08-23
Participants:

 Description   

A new invariant was added where operations that are holding open an oplog hole cannot try to acquire subsequent locks.

To temporarily circumvent this check, a new RAII-style class called IgnoreLockConstraintsOnTimestampedTxn was added to opt-out of the invariant.

There's a TODO in the codebase for this ticket. See SERVER-48129 for additional information.

The goal of this ticket should be to determine whether acquiring the lock can actually block in practice (perhaps another thread acquires a stronger lock).

 



 Comments   
Comment by Githook User [ 16/Aug/21 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-58219 Investigate ViewCatalog::reload() lock acquisition
Branch: master
https://github.com/mongodb/mongo/commit/d377ad57a16dcecd876b2b167f23d36b997fb96c

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