-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
v4.4, v4.2, v4.0
-
Service Arch 2021-03-08, Service Arch 2021-03-22, Service Arch 2021-04-05
-
(copied to CRM)
-
5
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.
- duplicates
-
SERVER-57007 MongoDB version 4.4.4 service crashed
- Closed
- is duplicated by
-
SERVER-52735 mongodb crash with "Invariant failure" opCtx != nullptr && _opCtx == nullptr
- Closed
-
SERVER-53857 Successive segfaults of several cluster members
- Closed
-
SERVER-59350 Invariant failure exception
- Closed
-
SERVER-60303 Mongodb PSS all nodes crashed
- Closed
- is related to
-
SERVER-53482 Invariant failure: opCtx != nullptr && _opCtx == nullptr in src/mongo/db/client.cpp, line: 126
- Closed
- related to
-
SERVER-49468 Invalidate previous OperationContext when a new OperationContext is created
- Closed
-
SERVER-52735 mongodb crash with "Invariant failure" opCtx != nullptr && _opCtx == nullptr
- Closed
-
SERVER-53857 Successive segfaults of several cluster members
- Closed
-
SERVER-53747 replica set down after setFeatureCompatibilityVersion 4.4
- Closed