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

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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0, 4.4.5, 4.0.24, 4.2.14
    • Component/s: None
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4, v4.2, v4.0
    • Sprint:
      Service Arch 2021-03-08, Service Arch 2021-03-22, Service Arch 2021-04-05
    • Case:
    • Story Points:
      5

      Description

      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. 

        Attachments

          Issue Links

            Activity

              People

              Votes:
              8 Vote for this issue
              Watchers:
              44 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: