[SERVER-21918] Remove cappedInFlight locks Created: 16/Dec/15  Updated: 06/Dec/22  Resolved: 29/May/18

Status: Closed
Project: Core Server
Component/s: Concurrency, Internal Code, Performance
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

We currently use locks on resourceCappedInFlightForOtherDb and resourceCappedInFlightForLocalDb to ensure that snapshots see a consistent point in time. Now that we single-thread all writes to non-oplog capped collections, this is probably unnecessary overhead. It is likely better (and still correct) to just lock the oplog in MODE_S while taking the snapshot. Part of this work will be to verify that this is the case.



 Comments   
Comment by Eric Milkie [ 29/May/18 ]

The cappedInFlight locks were removed some time ago.

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