The Fuzzer can run killOp on the JournalFlusher thread and cause it to throw an unexpected error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2021-04-19
    • 152
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The fuzzer appears to have run killOp against the journal flusher thread. At least, right after there's a log about killing op with opId 8221, the journal flusher gets interrupted with the same error message as OperationContext::checkForInterruptNoAssert, which can be called from the locking code (the journal flusher takes a lock to do a write to the oplogTruncateAfterPoint), can return.

              Assignee:
              Dianna Hohensee (Inactive)
              Reporter:
              Dianna Hohensee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: