[SERVER-86217] Checking if capped snapshot is needed can access collection metadata without synchonrization Created: 05/Feb/24  Updated: 06/Feb/24

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

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Catalog and Routing
Operating System: ALL
Participants:
Linked BF Score: 144

 Description   

When acquiring resources for an operation, we check whether we need need to establish a capped snapshot. This check then accesses the collection metadata. Notably, at this point we are using the latest version of the collection catalog since we haven't established a snapshot yet. This means that a concurrent operation can use the same version of the catalog to write to the collection metadata concurrently.


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