[SERVER-27961] Help to analyze diagnostic.data after crash with OOM Created: 09/Feb/17 Updated: 27/Oct/23 Resolved: 09/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Grigorii Eremeev | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: CentOS Linux 7 (Core) |
||
| Attachments: |
|
| Participants: |
| Description |
|
Hi! Could you help me please to analyze diagnostic.data from shard? |
| Comments |
| Comment by Alexander Gorrod [ 09/Feb/17 ] |
|
Grigorii It appears as though you have configured MongoDB to have a 40GB WiredTiger cache, with 47GB of system memory. As a starting point that doesn't leave much memory available for other processes on the system, so I would recommend configuring a smaller cache size. From the data you uploaded, I can see that only 32GB of cache where in use when the process was terminated, so 40GB is significantly above the amount of available memory on your system. It is also important to note that the WiredTiger cache size is not the total memory budget for MongoDB - it is only the memory allocated to cache data in order to minimize disk I/O. I'd recommend configuring a smaller WiredTiger cache size, and monitoring your system memory usage to see whether the amount of memory used by all processes is approaching your available cache size. This forum is for reporting bugs in MongoDB - wheras your question is about a configuration problem. If you have follow up questions you are better to ask on the MongoDB users google group. |