[SERVER-22082] Ability to specify minimum size for the connection pools from mongos -> mongod Created: 06/Jan/16 Updated: 08/Jan/24 Resolved: 24/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.6.11 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jared D. Cottrell | Assignee: | Backlog - Service Architecture |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
We would like to force our mongoses to create a pre-determined number of connections at startup without having to supply the load to use those connections first. The idea is to avoid the expense and delay of creating new connections at peak loads when every bit of resource counts by reserving the needed connections from the get-go. A parameter set at startup – perhaps connPoolMinShardedConnsPerHost – could work. |
| Comments |
| Comment by Mira Carey [ 24/May/19 ] |
|
ShardingTaskExecutorPoolMinSize was introduced in |
| Comment by Ramon Fernandez Marina [ 13/Jan/16 ] |
|
Thanks for your report jared, we've sent this to the Sharding team for consideration. Regards, |