[SERVER-14748] Capping mongos outbound connections to mongods Created: 31/Jul/14 Updated: 10/Dec/14 Resolved: 01/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Doug Haydon | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
For mongos, it appears prior to 2.6 the outbound connections to mongods were fixed to the number of inbound connections as configured in the java driver from a java client, but with 2.6 they are decoupled. What we are running into is although the inbound are capped with the setting, it appears the outbound are no longer capped. Is there some mongos setting available where we can cap the outbound connections to mongods in 2.6? |
| Comments |
| Comment by Ramon Fernandez Marina [ 01/Aug/14 ] |
|
Thanks for your report. The SERVER project is for reporting bugs or feature suggestions for the MongoDB server and tools. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. |