[SERVER-4466] Make mongos connection pool more configurable for users with large #s of shards Created: 09/Dec/11 Updated: 06/Dec/22 Resolved: 03/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.1.0 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
If users have very large numbers of shards, the default connection pool behavior may open too many unnecessary connections. It would be good to make this more configurable, at least to allow a configurable limit of baseline connections. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 11/Dec/11 ] |
|
I think the more important part is better multiplexing |