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

Allow durable updates to be evicted to the lookaside file

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT3.2.0, 4.1.9
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Storage Engines 2019-01-28, Storage Engines 2019-02-11, Storage Engines 2019-02-25, Storage Engines 2019-03-11

      Durable updates are currently treated as uncommitted from the point of view of eviction. We should allow them to be evicted to the lookaside file. We implemented most of the machinery required to do this as part of the original transaction prepare work. Since committing a prepared transaction now searches for updates via cursor operations, rather than referencing them directly in cache.

      This work involves:

      • Updating the timestamps tracked in WT_PAGE_LOOKASIDE to reflect durable timestamps instead of commit timestamps
      • Ensuring that checkpoint respects the durable timestamp for records even if they have been evicted to the lookaside table.
      • Creating a test validating that checkpoint sees the expected data
      • Ensure that entries in the lookaside file with durable timestamps can be cleaned up in a reasonable way

        1. test_dur.py
          4 kB
          Neha Khatri

            Assignee:
            neha.khatri Neha Khatri
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: