[SERVER-16950] Don't take exclusive lock on MinValid writes Created: 20/Jan/15  Updated: 06/Dec/22  Resolved: 21/Aug/18

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

Type: Improvement Priority: Trivial - P5
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-25545 Allow the opApplier and OplogWriter t... Closed
Related
is related to SERVER-16949 Don't take exclusive lock on MinValid... Closed
Assigned Teams:
Replication
Participants:

 Description   

This will need to be verified to be correct first, otherwise is cannot be done.

Note: The issue is that reading from oplog and writing oplog entries + minvalid are currently not allowed to happen at the same time (now, at least in the code). That will need to be allowable, in order to make this change. Also, this call is currently used to create the minvalid collection which requires at least an X-lock on the local db.



 Comments   
Comment by Mathias Stearn [ 23/Aug/16 ]

I will do this as part of SERVER-25545 otherwise the OpApplier and the OplogWriter won't actually be able to run in parallel.

Generated at Thu Feb 08 03:42:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.