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

failNonIntentLocksIfWaitNeeded failpoint interrupts lock requests in UninterruptibleLockGuard

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      STM 2019-08-12
    • Linked BF Score:
      0
    • Story Points:
      1

      Description

      Interrupting the lock request leads to a LockTimeout exception which is known not to be handled by the C++ code due to the presence of the UninterruptibleLockGuard and causes the server to abort. This issue was found during the rollback fuzzer where we suspect background thread (e.g. the TTL monitor) was holding an intent lock on the collection and prevented the collection lock acquisition in MultiIndexBlock::cleanUpAfterBuild() for a background index build from being acquired immediately.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              max.hirschhorn Max Hirschhorn
              Reporter:
              max.hirschhorn Max Hirschhorn
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: