[SERVER-9534] mongos v2.4.0 eats all memory, possible memory leak Created: 02/May/13 Updated: 10/May/13 Resolved: 10/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yu Feng | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | There is only one db which has two shards with each shard backed by 4 replica. |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Mongos consumes 14g+ of the 16g physical memory, smaps file is attached. Detail of mongos version: $ ldd mongos |
| Comments |
| Comment by Judotens Budiarto [ 10/May/13 ] |
|
i've same issue with Yu Feng and tried the 2.4.3 for last 4 days. it solved! thanks |
| Comment by Tad Marshall [ 10/May/13 ] |
|
Hi Yu, Thanks for letting us know! Tad |
| Comment by Yu Feng [ 10/May/13 ] |
|
The memory of version 2.4.3 stayed stable after 3 days of running, this issue may be closed. |
| Comment by Yu Feng [ 03/May/13 ] |
|
Thanks, Tad. I'll try the new versions and report the result here. |
| Comment by Christophe Spy [ 02/May/13 ] |
|
ok I do that but, in 2.4.1 I have the same memory leak than Yu Feng, I will follow the 2 problem |
| Comment by Tad Marshall [ 02/May/13 ] |
|
Hi Christophe, Thanks for the stack trace! This looks like a separate problem, and could be new. The stack trace shows that our V8 interface code is trying to allocate 128 MB for an object, which would never have worked in any version of MongoDB. Can you open a separate ticket for this problem and include information on the operations that were going on when the problem happened? Steps to reproduce would be ideal, but any information on how to get mongod into this state would be very helpful. Thank you! Tad |
| Comment by Christophe Spy [ 02/May/13 ] |
|
I have the same behavior : mongod consumme 100% of my RAM (32g) and then the server swap and oom killer kill mongod. I use mongo 2.4.1 (no shard, only replica set). I try 2.4.3 but after some hours mongod crash with another error : Thu May 2 13:46:03.265 [conn116] Assertion: 13548:BufBuilder attempted to grow() to 134217728 bytes, past the 64MB limit. |
| Comment by Tad Marshall [ 02/May/13 ] |
|
There were several memory-related issues addressed in version 2.4.2, including Can you try version 2.4.3, which includes all of the 2.4.2 fixes and is the current 2.4 version, and see if your problem is resolved? |