[SERVER-17472] "mongod" process missing, killed by OOM killer Created: 05/Mar/15  Updated: 06/Mar/15  Resolved: 06/Mar/15

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 3.0.0-rc11
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: liubei Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive log.zip    
Operating System: ALL
Participants:

 Description   

Environment:
3 sharding, (host:192.168.1.201~192.168.1.203, port:27017)
1 config server, (host:192.168.1.201, port:27019)
1 mongos. (host:192.168.1.201, port:27027)

OS:
CentOS 6.5

Driver:
mongo-java-driver 2.13.0
spring-data-mongodb 1.6.2.RELEASE

"mongod" process in host 192.168.1.203 is missing at multithread insert.
about detail, please check log file.(Occurred at "2015-03-05T07:52" )



 Comments   
Comment by Ramon Fernandez Marina [ 06/Mar/15 ]

Thanks for letting us know liubei. In general one can't go wrong adding more memory, but I think it's good practice to always have enough swap space around to allow the system to degrade gracefully under load. One common approach is to have a swap space that's twice the size of the physical memory.

If you have further questions about memory configuration for MongoDB 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

Comment by liubei [ 06/Mar/15 ]

Ramon Fernandez, Thank you very much! indeed the OOM killer terminated “mongod”.

Then, this mean that I need to increase the physical memory? Can you give me some suggestions? Thanks again!

Comment by Ramon Fernandez Marina [ 05/Mar/15 ]

liubei, what I see in the logs is that mongod in 192.168.1.203 is unavailable to mongos for a period of time, but the logs for that mongod show entries until 2015-03-05T08:52:11.775+0800. Is it the case that mongod was no longer running after that log entry? Or that mongos had trouble communicating with it for a period of time?

If the mongod process stopped running in 192.168.1.203, and you please check your system logs on that host? Look for messages saying "killed process" to see if the OOM killer terminated mongod.

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