[SERVER-11891] Mongodb client connections get dropped quickly, leaving sockets in WAIT state. Created: 28/Nov/13 Updated: 10/Dec/14 Resolved: 13/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pieter Willem Jordaan | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 13.10 x86_64, Boost 1.55/1.54 |
||
| Issue Links: |
|
||||
| Operating System: | Linux | ||||
| Steps To Reproduce: | Install mongodb 2.5.4, use 1000+ threads with ScopedDBConnection |
||||
| Participants: | |||||
| Description |
|
When making connections to MongoDB from the C++ client driver, in the order of thousands, connections get dropped rapidly. This leaves too many sockets in the WAIT state when monitoring with netstat -nat | grep WAIT. This causes the application to be unable to create new connections to MongoDB and in turn becomes idle. Also CPU usage increases to almost 80% of the test computer's capacity during this phenomenon. During this process mongostat provides no insight as nothing database oriented is happening. |
| Comments |
| Comment by Pieter Willem Jordaan [ 13/Dec/13 ] |
|
The connections dropping was due to test code that got inserted while trying to pinpoint performance issues. I was unable to pinpoint. I think this ticket may be closed until I can find more information. |
| Comment by Eliot Horowitz (Inactive) [ 30/Nov/13 ] |
|
How are you closing the connections on the driver? |