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

Update lookaside schema to store durable timestamp

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT3.2.0, 4.1.8
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • Storage Engines 2019-01-28

      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:

      • Ensuring the durable timestamp is written to the lookaside file
      • Ensuring the durable timestamp is read from the lookaside file
      • Create a test to simulate the cache stuck for updates with durable timestamp > stable timestamp. During checkin reduce the number of updates so that cache stuck will not happen.

            Assignee:
            neha.khatri Neha Khatri
            Reporter:
            vamsi.krishna@mongodb.com Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: