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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.3
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Execution Team 2019-12-16
    • Linked BF Score:
      48

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: