-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
None
-
Affects Version/s: 4.4.0, 4.4.1
-
Component/s: Stability, WiredTiger
-
None
-
ALL
-
-
(copied to CRM)
-
119
Hi
We have been getting infrequent (1-2 times a day) aborts of this kind lately. This happened on 4.4.1 and 4.4.0 too. We have had years without issue (3-node replica set), upgrading as new versions come around. It isn't tied to specific times either.
This is on an AWS I3 instance with nvme drive, formatted to xfs.
Snippet of the logs here and in the attachement.
We have tried removing the DB path and resyncing from a secondary, but this did not fix it.
What could cause this? Could it be a specific query? Could the disk itself be corrupt? How can I help pinpointing the issue?
- is related to
-
SERVER-50880 Mongod Server Failed with signal 6
- Closed
-
SERVER-51386 Mongo 4.4.1 Crashes often
- Closed
- related to
-
WT-6811 Allow older readers to read behind a mixed-mode operation
- Closed
-
WT-6928 Removing historical updates required by the old reader session
- Closed
-
SERVER-52530 Mongo v.4.4.1 crash - UnknownError -31803: WT_NOTFOUND
- Closed