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

Improve log preallocation algorithm

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.5, 4.1.6, WT3.2.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Engines 2018-11-19

      The current log file preallocation algorithm, which is implemented in the __log_server function has a few aspects that should be improved:

      • The loop uses a timer - but it only waits around a condition variable - it should instead re-set only when a preallocated log file is created. It's possible with the current implementation that some workloads won't pre-allocate log files.
      • I'm concerned that preallocation waits for the hot backup lock - which can be held for a long time if a hot backup is in progress. A try lock might be better in the code - to avoid other operations done by the log server being starved.

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: