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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0-rc0
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Execution Team 2021-04-19
    • Linked BF Score:
      152

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            dianna.hohensee Dianna Hohensee
            Reporter:
            dianna.hohensee Dianna Hohensee
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: