[SERVER-19817] mongod crash "cannot allocate memory" during aggregate Created: 07/Aug/15  Updated: 07/Aug/15  Resolved: 07/Aug/15

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

Type: Bug Priority: Critical - P2
Reporter: Remi Jolin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File crash-mongod.log    
Issue Links:
Duplicate
duplicates SERVER-17364 Idle cursors shouldn't hold storage e... Closed
Operating System: ALL
Participants:

 Description   

While reading data from a sharded db (within an aggregate), mongod crashes with the following message :

2015-08-07T11:21:08.540+0200 E STORAGE  [conn2135] WiredTiger (12) [1438939268:540151][8073:0x7f07fb4f7700], connection.open_session: only configure
d to support 20010 sessions (including 10 internal): Cannot allocate memory
2015-08-07T11:21:08.540+0200 I -        [conn2135] Invariant failure: ret resulted in status UnknownError 12: Cannot allocate memory at src/mongo/db
/storage/wiredtiger/wiredtiger_session_cache.cpp 49

(Full log extract around the crash attached)



 Comments   
Comment by Ramon Fernandez Marina [ 07/Aug/15 ]

rj-10gen@arsynet.com, the error message and stack trace seem to indicate this is a duplicate of SERVER-17364, which was fixed in the 3.0.5 stable version as part of SERVER-17386. You can see a more detailed explanation with workarounds here.

Regards,
Ramón.

Generated at Thu Feb 08 03:52:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.