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

Reconsider error path in log server thread

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.4, 3.4.14, 3.7.3, WT3.1.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2018-02-26
    • v3.6, v3.4

      In SERVER-33187 a customer database stopped archiving log files (on a Windows system). The pre-allocation of log files also stopped. FTDC data indicated that everything else seemed normal and checkpoints were happening normally. Nothing was out of the ordinary. I determined that the reason was that the log server thread exited and found its error message in the logs.

      The system kept running but there was now no thread to ever perform the tasks of that thread. So WT log files kept accumulating forever. This was a Windows system, and an attempt to remove a log file got Access Denied/EPERM.

      We should review internal thread error path handling. Perhaps any internal thread error should be fatal and cause a panic. Or internal threads should handle errors more specifically and perhaps retry for some potentially transient errors.

            sue.loverso@mongodb.com Susan LoVerso
            sue.loverso@mongodb.com Susan LoVerso
            2 Vote for this issue
            12 Start watching this issue