[SERVER-18026] possible leak memory of mongos Created: 14/Apr/15 Updated: 22/May/15 Resolved: 22/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | 2.4.11, 2.4.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jiangcheng Wu | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Each mongos eat about more than 1.5GB RSS memory after running for about 2 months of all instances. It possible exist memory leak.
and this one eat 500MB RSS memory after running for about 10 days
and some other info
|
| Comments |
| Comment by Ramon Fernandez Marina [ 22/May/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks for the update wujiangcheng. I just wanted to bring another datapoint that may be relevant, and is Another possible explanation for the memory consumption you're seeing is if your collections have a large number of chunks, as mongos need to keep chunk information which consumes memory. That being said, the most common culprit is open cursors, so now that you've lowered the idle cursor timeout you should see a lower memory footprint. Since we couldn't find evidence of a bug in the server or mongos I'm going to resolve this ticket, as we keep the SERVER project 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. Regards, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Jiangcheng Wu [ 12/May/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi, We have upgraded our mongos to 2.4.14 and will see if it's ok
mongod:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Sam Kleinman (Inactive) [ 16/Apr/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
We've looked over this case a bit more, and I wanted to provide a bit more context as to our thinking. In addition to memory leaks, the kind of behavior that you're seeing can also result from situations where you have too many open cursors, or where cursors are not correctly timing out. I think we can do without logs for now, but the following data may help a bit more:
Hopefully we can quickly isolate cursor use and figure out what's going on here. Thanks and sorry about any confusion. Regards, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Sam Kleinman (Inactive) [ 14/Apr/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks for the report. I have a few additional questions, that will help us narrow down the cause of this issue:
Thanks, and I hope that we can help you resolve this promptly. Cheers, |