Fix LSM worker thread ID usage

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None

      In WiredTiger LSM, each worker thread currently gets assigned an ID. That ID is used to determine how large a merge that thread will choose to do.

      The functionality is a hang over from when each tree had it's own set of worker threads.

      We should review when we allow larger merges to be undertaken. The thread ID scheme is no longer relevant.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: