[SERVER-22439] mongod process stops when multiple processes in same server Created: 02/Feb/16 Updated: 05/Feb/16 Resolved: 05/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Juan Manuel Diego G | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | In a single server have three mongod processes running at the same time, each one of them is a replica of different shards, and each shard is using around 40Gb in the SDD. The initial sync of the last one of them tends to stop the other two and when the three are finally up, they stop randomly. |
| Participants: |
| Description |
|
When a single server has multiple mongod processes running, some of them will stop randomly. After a service has stopped, there is no log reporting any error, it just stops. |
| Comments |
| Comment by Kelsey Schubert [ 05/Feb/16 ] |
|
Hi jdiego@digital-legends.com, The behavior you describe is likely due to running out of memory on the host. You may confirm this by checking your system logs on the host: look for messages saying "killed process" to see if the OOM killer terminated mongod. We recommend increasing the amount of memory on your host to allow performance to gracefully degrade. You may also want to consider using cgroups or containers to limit the RAM for each mongod. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. Thank you, |