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

failNonIntentLocksIfWaitNeeded failpoint interrupts lock requests in UninterruptibleLockGuard

    • Fully Compatible
    • ALL
    • v4.2
    • STM 2019-08-12
    • 0
    • 1

      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.

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

              Created:
              Updated:
              Resolved: