[SERVER-21805] RAM usage - slow down server Created: 09/Dec/15 Updated: 09/Dec/15 Resolved: 09/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Niti Test | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | 1. RS with WT |
| Participants: |
| Description |
|
We have a replica set with one secondary and one arbiter (each on a different server) and moved from MMapv1 to WiredTiger. Primary and Secondary each have 32 GB. We have now a process where we read each document once. The mongod process uses all of the 32 GB RAM and the server is very slow. free -m output: |
| Comments |
| Comment by Ramon Fernandez Marina [ 09/Dec/15 ] |
|
k9908600@gmx.at, there are some known issues with excessive memory consumption in early 3.0 versions, so I'd recommend you upgrade to 3.0.7. Note that 3.2.0 was released yesterday and contains many improvements in this area, as well as new features and performance enhancements, so you may want to give 3.2.0 a try. Both for 3.0 and 3.2 you should be aware of the WiredTiger cache size and can try lowering its value. Please note that 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. See also our Technical Support page for additional support resources. Regards, |