|
I think this is likely memory corruption, we should review the system logs to see if there are any reported problems, and perhaps check for heat problems in the data center.
I suspect bad memory because:
- there are 3 different stacks, all of the stacks are in heavily exercised WiredTiger code paths,
- these are all unique failures for the MongoDB release (we haven't had any other customer or user experience segment faults in these paths), and
- although it's difficult to prove, the reference that's likely failing shouldn't have been the first reference to that memory location in the particular code path.
anonymous.user notes these failures are from different servers, which makes hardware failure less likely, but regardless, I think this is unlikely to be a software bug.
|