[SERVER-23937] Crash reported as OOM, but that's very unlikely Created: 26/Apr/16  Updated: 24/May/16  Resolved: 24/May/16

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tomasz Grzywalski Assignee: Kelsey Schubert
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AWS with Ubuntu 14.04, 16GB RAM, MongoDB 3.2.3


Attachments: File mongodb_crash.log    
Operating System: Linux
Participants:

 Description   

The database crashed with OOM error, but that's very unlikely. After restart it uses only 6GB RAM and only 20% storage space. After restart all runs normally. Attached relevant log portion.



 Comments   
Comment by Kelsey Schubert [ 17/May/16 ]

Hi stommager,

We still need the diagnostic data to investigate this problem. If this is still an issue for you, can you please upload the complete logs and an archive of the $dbpath/diagnostic.data directory when this behavior occurs?

Thank you,
Thomas

Comment by Kelsey Schubert [ 26/Apr/16 ]

Hi stommager,

Thank you for opening this ticket. So we can continue to investigate this issue, please archive (tar or zip) the $dbpath/diagnostic.data directory and attach it to this ticket.

Additionally, please provide the complete logs so we can correlate the diagnostic data to events recorded in the log.

Kind regards,
Thomas

Comment by Keith Bostic (Inactive) [ 26/Apr/16 ]

ramon.fernandez, stommager, I don't see evidence this is specifically a WiredTiger issue (it's just the OOM occurred in the WiredTiger integration layer). For now, so I'm moving it into SERVER triage. Hope that's correct!

Generated at Thu Feb 08 04:04:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.