Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-3531

Provide a way to flush the log if commits were out of timestamp order

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
      None
    • Case:
    • Sprint:
      Storage 2017-09-11, Storage 2017-10-02

      Description

      MongoDB 3.4 had an optimization when tracking commits that avoided flushing the log if transactions committed in order. To get the same behavior in 3.6, we need to track whether transactions are committing in order and use that information to optionally sync the log to disk.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-storage-engines Backlog - Storage Engines Team
              Reporter:
              michael.cahill Michael Cahill
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated: