[SERVER-66341] Improve journal flusher locking behavior Created: 10/May/22  Updated: 14/Dec/23  Resolved: 14/Dec/23

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Josef Ahmad
Resolution: Duplicate Votes: 0
Labels: car-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-66342 Remove resourceIdFeatureCompatibility... Closed
Duplicate
duplicates SERVER-66340 Improve distributed transaction commi... Closed
Related
related to SERVER-65821 Deadlock during setFCV when there are... Closed
is related to SERVER-66340 Improve distributed transaction commi... Closed
Assigned Teams:
Catalog and Routing
Sprint: Execution Team 2022-10-17, CAR Team 2023-12-25
Participants:
Story Points: 3

 Description   

Currently the journal flusher runs on its own thread and performs a few actions, including updating the oplog truncation point document. This particular action means that the journal flusher has to take global/db/collection locks, which can be problematic as seen in SERVER-65821. We should investigate ways to improve this behavior so that we can remove the workaround added in that ticket.



 Comments   
Comment by Josef Ahmad [ 14/Dec/23 ]

Closing as a duplicate of SERVER-66340 which resolved the class of deadlocks involving non-intent global lock requests in the presence of a transaction in the prepared state.

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