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

Update the oldest transaction ID from eviction

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • WT2.7.0
    • Affects Version/s: None
    • Component/s: None
    • None

      It is important that WiredTiger's tracking of the oldest transaction ID doesn't fall too far behind, or some operations become slower from keeping around versions unnecessarily.

      We have tried having transactions update the oldest ID themselves, but that adds extra work into critical paths, and needs care to avoid getting tangled up with application threads own updates to transaction state.

      Instead, have the eviction server update the oldest ID every time it wakes up (at the same time it updates the read generation). This should be frequent enough to prevent the oldest ID falling a long way behind current, and simplifies ordinary transactions.

            Assignee:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Reporter:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: