[SERVER-30858] OOM Killer Killing mongo Created: 27/Aug/17 Updated: 16/Nov/21 Resolved: 12/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | suresh narasimhan | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
I have a 3 replicaset mongo cluster version 3.2.10, Recently we are haveing an issue of OOM killer killing mongod process , we upgraded the version to c3.2xlarge in aws and the crash still happened. we did not have a swap space configured and have configured it after the crash. mm shows about 300 connections to mongo , I am not clear why mongo eats up so much ram inspite of the DB size being so small for the OOM killer to kill it. I did see an expensive query that ran for 2 secs that might have did a full table scan that might have run just before the OOM killer kill The incident happened about 9.54 AM PST on Aug 26 attaching mongo logs and diagnostic data https://drive.google.com/file/d/0B0DcYD8YgYOJMmZTcVNLUXlTdDQ/view?usp=sharing https://cloud.mongodb.com/v2/50366375f1a5dd0b002fab66#host/replicaSet/5615733ee4b009c743f75edf
|
| Comments |
| Comment by Kelsey Schubert [ 29/Sep/17 ] |
|
Hi snarasimhan, We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide us access to the syslog? Thank you, |
| Comment by Kelsey Schubert [ 07/Sep/17 ] |
|
Hi snarasimhan, I do not have access to view these files. Would you please upload the requested files to our secure upload portal? Thank you, |
| Comment by suresh narasimhan [ 28/Aug/17 ] |
| Comment by Kelsey Schubert [ 28/Aug/17 ] |
|
Hi snarasimhan, Would you please provide the syslog covering this event? Thank you, |
| Comment by suresh narasimhan [ 27/Aug/17 ] |
|
I was using the default wiredTiger cacheSize , have restricted the cacheSize to 3G (slightly more than compressed data size) |