-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.4.4
-
Component/s: None
-
None
-
ALL
All of the nodes in the cluster crashed abruptly. Upon checking the mongodb logs, we pulled out these:
{"t":\{"$date":"2021-09-27T20:57:28.439+00:00"},"s":"F", "c":"-", "id":23079, "ctx":"monitoring-keys-for-HMAC","msg":"Invariant failure","attr":{"expr":"opCtx != nullptr && _opCtx == nullptr","fi
le":"src/mongo/db/client.cpp","line":126}}
{"t":
,"s":"F", "c":"-", "id":23080, "ctx":"monitoring-keys-for-HMAC","msg":"\n\n***aborting after invariant() failure\n\n"}
{"t":
,"s":"F", "c":"CONTROL", "id":4757800, "ctx":"monitoring-keys-for-HMAC","msg":"Writing fatal message","attr":{"message":"Got signal: 6 (Aborted).\n"}}
Upon searching, we landed on multiple Jira issues reporting the same. This particular link: https://jira.mongodb.org/browse/SERVER-57007 says that the issue has been resolved in version 4.4.5. However, in the release notes 4.4.5 it's not clear if it has been fixed in this version.
We'd like to know if it has been fixed yet in any of the versions or should we downgrade to a lower version?
- duplicates
-
SERVER-53566 Investigate and reproduce "opCtx != nullptr && _opCtx == nullptr" invariant
- Closed