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

Reduce LSM cache requirements with old readers

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: LSM
    • Labels:
      None

      The LSM data source keeps content pinned in cache to satisfy old readers. With the new timestamp support in MongoDB having older readers has become more normal. We should revisit some LSM design decisions about restricting when chunks are flushed to make sure they don't lead to hangs when there are old readers (or a big gap between oldest timestamp and current timestamp).

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: