[SERVER-5356] mongos OOM Created: 22/Mar/12 Updated: 15/Aug/12 Resolved: 10/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | guojiangyong | Assignee: | Randolph Tan |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | mongos | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
mongodb(cnf)+mongodb(db)+mongos |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
mongodb(cnf)+mongodb(db)+mongos |
| Comments |
| Comment by Ian Whalen (Inactive) [ 03/May/12 ] |
|
@guojiangyong, can you possibly get these machines into MMS and also add some clarification to what kind of ops you are running on these machines? |
| Comment by Randolph Tan [ 03/Apr/12 ] |
|
Hi, Would it be possible to run these machines on MMS (http://wiki.mongodb.org/display/DOCS/MongoDB+Monitoring+Service). It would also be very helpful if you describe what kind of operations you are running on these machines. |
| Comment by guojiangyong [ 31/Mar/12 ] |
|
1.it is the physical memory usage. |
| Comment by Randolph Tan [ 29/Mar/12 ] |
|
@guojiangyong - Some questions: 1. What is the graph plotting? Is it the physical memory usage for the machine? or mongos? or mongod? or mongos + mongod? @patrick & @guojiangyong 2. How many connections do you have when it run out of memory? |
| Comment by Patrick Neff [ 29/Mar/12 ] |
|
edit: I think this is an overcommit issue let me fix that and see if it works better. I'm having the same problem but with a capped collection. My system has 16GB of ram and the collection is set to 8GB with a resulting 3.5GB of indexes. This should fit in memory just fine and does for about 12 hours. Then it gets OOM'd. Typical load is much higher during the day then at night and runs fine under load. The system is under relatively light load when it get OOM'd. Heck I was shrinking the size of the capped collection to 8GB to see if a smaller collection would fix it and was using greater than 100% of memory somehow and everything still ran fine. CentOS 6 64-bit |
| Comment by guojiangyong [ 26/Mar/12 ] |
|
First thank you very much! strace -c -f -p monogs PID % time seconds usecs/call calls errors syscall |
| Comment by Randolph Tan [ 22/Mar/12 ] |
|
Hi, I noticed that you set the Tests Written field as Complete. Would you mind attaching the test? Can you also provide more details about your environment?: 1. Number of shards (and whether they are replica sets) If you don't have the test, can you describe the type of load you have in your system? For example you run several concurrrent map reduce jobs, etc. |