[SERVER-4127] appears to be a memoryleak in mongodump Created: 23/Oct/11 Updated: 29/May/12 Resolved: 03/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dave Mitchell | Assignee: | Brandon Diamond |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | leak, mongodump | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
observed under both mac os x and windows |
||
| Operating System: | ALL |
| Participants: |
| Description |
Let me know what additional details I can provide that might be helpful. |
| Comments |
| Comment by Brandon Diamond [ 02/Mar/12 ] |
|
Abhi, thanks for bringing that to our attention. Can you please open a new ticket describing your issue? |
| Comment by Abhishek Pratap [ 01/Mar/12 ] |
|
Any progress on this...I am experiencing similar issues. I loaded about 200 million records in the db. before loading the server running had 25 Gb for free RAM. I have now killed the MongoDB and still see memory being used. -Abhi |
| Comment by Brandon Diamond [ 01/Nov/11 ] |
|
Haven't heard anything for awhile. Has anything changed? Otherwise, we'll close out this ticket tonight. |
| Comment by Brandon Diamond [ 25/Oct/11 ] |
|
Very odd – let's take a look. Any chance you're in (or can add) MMS? This would help us troubleshoot the issue tremendously. |
| Comment by Eliot Horowitz (Inactive) [ 25/Oct/11 ] |
|
Are you looking at resident or virtual? |
| Comment by Dave Mitchell [ 25/Oct/11 ] |
|
It's now looking more like an issue in the mongo core, rather than the tools – if I simply loop over all the items in the collection, I see the same issue--memory grows dramatically in the mongodb process, and is not freed. Could this really be? Sounds pretty serious, if it's not just me or my environment. Am running production release of 2.0.1 on both osx and win64. |
| Comment by Dave Mitchell [ 24/Oct/11 ] |
|
The mongorestore leaks as well. I can watch the memory rise as I restore the collection (using mongorestore --drop -d mydatabase -c mycollection location). Clearly a 1:1 – importing a 6gb collection means the memory allocated to the mongo server goes up by rougly 6gb, and is not released ontil I manually start and stop the service. |