[SERVER-8442] Map-reduce memory leak Created: 02/Feb/13 Updated: 11/Jul/16 Resolved: 15/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce, Sharding |
| Affects Version/s: | 2.2.2, 2.2.3, 2.3.2 |
| Fix Version/s: | 2.2.4, 2.4.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Reproduced on Ubuntu 12.04.1 LTS and OS X |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: | To reproduce: |
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Non-mapped virtual memory grows on a mongod primary while map-reduce jobs are run. This leads to bouncing the primary once a day to prevent OOM failures. This happens on a single shard of a sharded cluster. Also attached is valgrind massif output from both shards. From the shard1 file you will see memory allocated in the following grow throughout the run:
|
| Comments |
| Comment by auto [ 20/Mar/13 ] |
|
Author: {u'date': u'2013-02-08T19:03:14Z', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 11/Feb/13 ] |
|
Author: {u'date': u'2013-02-08T19:03:14Z', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: |
| Comment by James Wahlin [ 04/Feb/13 ] |
|
Attached valgrind massif output for both shards during map-reduce job. |
| Comment by James Wahlin [ 02/Feb/13 ] |
|
As part of investigation please see whether there are any workarounds that can be used for MongoDB 2.2.2. |