Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
4.4.4
-
Fully Compatible
-
ALL
-
v5.0, v4.4
-
Sharding 2021-05-03, Sharding 2021-05-31
Description
{"t":{"$date":"2021-04-08T13:25:49.833+00:00"},"s":"F", "c":"-", "id":23079, "ctx":"conn21888","msg":"Invariant failure","attr":{"expr":"!hasTransientTransactionOrRetryableWriteError","file":"src/mongo/db/error_labels.cpp","line":124}}
|
{"t":{"$date":"2021-04-08T13:25:49.833+00:00"},"s":"F", "c":"-", "id":23080, "ctx":"conn21888","msg":"\n\n***aborting after invariant() failure\n\n"}
|
{"t":{"$date":"2021-04-08T13:25:49.839+00:00"},"s":"F", "c":"CONTROL", "id":4757800, "ctx":"conn21888","msg":"Writing fatal message","attr":{"message":"Got signal: 6 (Aborted).\n"}}
|
Attachments
Issue Links
- related to
-
SERVER-54534 No need to wait for writeConcern on aborting a multi-document transaction
-
- Closed
-