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

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

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage 2017-09-11, Storage 2017-10-02

      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.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: