Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-45135

WTCheckpointThread throws LockTimeout when 'failNonIntentLocksIfWaitNeeded' is enabled and the CheckpointLock is held by another thread

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Execution Team 2019-12-16
    • 48

      The 'failNonIntentLocksIfWaitNeeded' fail point will immediately throw a LockTimeout exception even if the deadline is set to Date_t::max() when the WTCheckpointThread cannot immediately acquire the CheckpointLock because another thread is holding it.

      This is only happening on the fuzzer because it enables that fail point.

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: