Info
The huge memory consumption of mongodb resulted in a kernel panic...
More details on the mongod/OS versions:
Thu Jan 22 12:19:42 [initandlisten] MongoDB starting : pid=4581 port=27017 dbpath=/data/db/ 64-bit host=verspertine
Thu Jan 22 12:19:42 [initandlisten] db version v2.0.6, pdfile version 4.5
Thu Jan 22 12:19:42 [initandlisten] git version: nogitversion
Thu Jan 22 12:19:42 [initandlisten] build info: Linux z6 3.8-trunk-amd64 #1 SMP Debian 3.8.3-1~experimental.1 x86_64 BOOST_LIB_VERSION=1_49
Thu Jan 22 12:19:42 [initandlisten] options:
{ verbose: true }
Top User Comments
ramon.fernandez commented on Thu, 22 Jan 2015 21:29:26 +0000:
Thanks for your report liar666. Depending on the size of your dataset MongoDB may require significant amounts of memory, and if the OS detects too much memory usage by any process the OOM killer may step in and kill that process.
If the OOM killer is not working as expected this is not a bug in MongoDB itself. You may also want to add more swap to your system and/or follow up with your OS vendor.
Since this is not a bug in MongoDB I'm resolving this ticket, as the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group.
Regards,
Ramón.
