[SERVER-28959] Mongo memory usage is increasing gradually Created: 25/Apr/17 Updated: 27/Apr/17 Resolved: 27/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.4 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Sathish Babu [X] | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
We are using Mongo DB 3.2.4 replica set with Wired Tiger Storage engine. The replicaset consists of 1 primary 1 secondary and 1 arbiter. Primary and Secondary memory size is 62 gb. The data size is 8 GB. Issue Description : Mongo memory usage initially was 45% and gradually increased over the period to 50 and now to 58% in both primary and secondary server. Given below the mongo stat, mongo top. Attached the diagnostic data files with this ticket.
|
| Comments |
| Comment by Ramon Fernandez Marina [ 27/Apr/17 ] |
|
There have been many improvements on memory management since version 3.2.4, so I'd recommend upgrading to the latest version and, if you believe there's a bug or a leak, open a new ticket for us to investigate. 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, |
| Comment by Sathish Babu [X] [ 27/Apr/17 ] |
|
Hi, Kindly update on this. Thanks, |