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

Change to explicitly journal a subset of content in WiredTiger

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.11
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Storage 2017-05-29, Storage 2017-07-10, Storage 2017-07-31

      Description

      The architecture of the WiredTiger storage engine implementation means that MongoDB maintains two copies of data to guarantee durability, one in the oplog the other in the WiredTiger log (journal). It is only necessary to ensure that the content of the oplog is made durable to the current guaranteed durability point, since the oplog can be used to "recover" the content in other collections after a crash.

      This work encompasses switching which content is journaled when using the WiredTiger storage engine.

      There are cases where the storage engine will need to keep journaling as it does today - in any configuration where the oplog isn't enabled, so it makes sense to add this feature alongside the current method of journaling. Perhaps we need a new (or expanded) parameter to the KVEngine constructor to decide which journaling mode to use.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              daniel.gottlieb Daniel Gottlieb
              Reporter:
              alexander.gorrod Alexander Gorrod
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: