[SERVER-17334] Runs out of sessions on capped collection during load test (WT, not MMAP) Created: 20/Feb/15 Updated: 12/Oct/15 Resolved: 27/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.0-rc8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Christian Amor Kvalheim | Assignee: | Bruce Lucas (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
osx 10.10 yosemite, mongodb-rc8 and mongodb-rc9 (master) |
||
| Attachments: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Steps To Reproduce: | 2 processes with 50 connections each generate 1000 inserts a second into a capped collection while there is 2 processes that continuously query the capped collection using tailed cursors and closing after the first document is received. After a while the server exits with not able to allocate memory I'll be happy to help anyone who wants to reproduce the issue (tested against RC8 and current master) Reproduce steps
Wait for mongod process to fail |
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
| Comments |
| Comment by nicolas roux [ 12/Oct/15 ] |
|
We had the same problem with 3.0.6. After a long tracking of unclosed connection, we could reset timeout to 10 minutes |
| Comment by Ramon Fernandez Marina [ 02/Apr/15 ] |
|
Hmmm, I see. You may be interested in trying out the 3.0.2-rc0 release candidate that was published earlier today, as it includes |
| Comment by Artem Volkhin [ 02/Apr/15 ] |
|
Ramon, thanks for the reply. I'm still investigating the problem, but looks like I can reproduce when connecting to replicaset through mongos and never when connecting directly to the replicaset from my application. So it looks like I can't fix how mongos handle opened sessions. |
| Comment by Ramon Fernandez Marina [ 02/Apr/15 ] |
|
volkhin, this behavior is triggered when an application opens too many cursors and/or doesn't close them fast enough. This ticket is actually a duplicate of |
| Comment by Artem Volkhin [ 02/Apr/15 ] |
|
Same problem happened to me. Any progress on this? |