Investigate and reproduce "opCtx != nullptr && _opCtx == nullptr" invariant

XMLWordPrintableJSON

    • Fully Compatible
    • v4.4, v4.2, v4.0
    • Service Arch 2021-03-08, Service Arch 2021-03-22, Service Arch 2021-04-05
    • 5
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      There seems to be an unknown issue causing a particular invariant to occasionally get hit, which results in nodes unexpectedly terminating. The invariant is improved as part of SERVER-49468 but this ticket is to track a root cause investigation.

      Someone needs to spend some dedicated time in order to try and unwind what may be happening here and determine the steps required to reproduce this particular bug. 

      Acceptance Criteria:  Either:

      • A set of procedures that a user might be able to implement which causes the invariants to trigger. 
      • A plan for how to add additional, backportable, diagnostic data that will allow us to properly track down the cause of this invariant being triggered. 

            Assignee:
            Tyler Seip (Inactive)
            Reporter:
            Matthew Tretin (Inactive)
            Votes:
            8 Vote for this issue
            Watchers:
            46 Start watching this issue

              Created:
              Updated:
              Resolved: