[SERVER-17047] MongoD aborts when running under memory pressure Created: 26/Jan/15 Updated: 03/Feb/15 Resolved: 26/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.0.0-rc6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eitan Klein | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | Configured Windows 8 on HyperV environment and assign low amount RAM for quick repro Environment
|
||||
| Participants: | |||||
| Description |
|
Dump file \\eitan6\tmp\eitan8av.dmp The log file indicated Invariant failure(see below)
If I understand correctly the crash happen because WT ONLY reported about the error, however, the evict thread executed before the invariant kicked in and blocked a graceful termination of the Mongod.
000000c0`71ccf950 00007ffc`b9e16a16 ntdll!RtlReportCriticalFailure+0x8c
|
| Comments |
| Comment by Mark Benvenuto [ 26/Jan/15 ] |
|
I am closing this as by design. The times in the dump file (i,e the stack in the bug) do not line up with the log file so I cannot say anything about cause/effect. I believe it may be a double free or overwrite, but it will like not repro easily. You would need to trap in the debugger, and use the various !heap commands in inspect it. The abort/rude shutdown is expected in this case. When WT returns an unexpected status code (basically any error generally), we raise an invariantWTOK which aborts the server. This means when WT hits OOM, out of disk space, etc, we shutdown since we do not have special error handling code for the arbitrary OS errors that WT may return. |