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

Improve clarity in LSM merge selection algorithm

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

      The code in __lsm_merge_span is confusing when attempting to understand what youngest_gen and youngest variables track.

      The youngest_gen variable appears to sensibly track what the variable name implies, but youngest appears to track the chunk currently being considered. We should update the code so that it's intent is clearer.

            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: