Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42477

Make checkpointing a general storage engine concept, rather than wiredtiger specific

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution

      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.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: