[SERVER-42477] Make checkpointing a general storage engine concept, rather than wiredtiger specific Created: 29/Jul/19  Updated: 06/Dec/22  Resolved: 08/Jun/20

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29418 Create a storage-engine agnostic chec... Closed
Related
related to SERVER-42221 Add concurrency control to checkpoint... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

The collection validate cmd must run mutually exclusively with taking WT checkpoints. This requires a mutex being taken in the WT engine implementation code, as well as at the MongoDB command level.

SERVER-42221 will add such a mutex, by putting it in the StorageEngineImpl class and creating a factory class to return a ExclusiveLock on the mutex through the StorageEngine interface.

However, the more ideal solution appears to be to elevate the checkpoint concept into the StorageEngine interface such that we can cover checkpoint by locking a mutex around a StorageEngine call. Then we would not have a mutex trying providing service across many abstraction layers.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 26/Aug/19 ]

Should wait for SERVER-29418 and then reevaluate what's left to do, if anything.

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