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

Create a storage-engine agnostic checkpointing thread

    XMLWordPrintableJSON

Details

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.8.0
    • None
    • Storage
    • None
    • Fully Compatible
    • Execution Team 2019-08-26, Execution Team 2020-09-07, Execution Team 2020-09-21
    • 39

    Description

      SERVER-29210 moved WiredTiger's checkpointing thread into MongoDB such that it can later be coordinated with replication to only persist to disk majority committed updates (and the entirety of the oplog). Updates that are not majority committed will only modify in-memory data structures. This will make rollbacks simpler by reverting to the on-disk data and rolling forward the updates that survived the rollback.

      This ticket is for exposing this functionality across storage engines by (presumably) allowing them to opt-in to some new storage engine API methods and pulling the checkpoint thread up a level.

      Attachments

        Activity

          People

            gregory.wlodarek@mongodb.com Gregory Wlodarek
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: