[SERVER-32380] established connections keep larger than connPoolMaxShardedConnsPerHost Created: 18/Dec/17 Updated: 11/Jan/18 Resolved: 21/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.2.17 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Adun | Assignee: | Kelsey Schubert |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
1. mongos run with: --setParameter connPoolMaxShardedConnsPerHost=10
from the mongos log, i found:
but I found there are still 22 connections from mongos to mongod(10.160.243.108), netstat command as below:
the 22 connections will always keep established. the output as below:
so, may I have a wrong use on connPoolMaxShardedConnsPerHost ? official docs about connPoolMaxShardedConnsPerHost:
|
| Comments |
| Comment by Kelsey Schubert [ 21/Dec/17 ] |
|
Thanks for reporting this behavior. Just earlier today, we improved this behavior in the master branch of MongoDB. Please review Sam's comment on Kind regards, |
| Comment by Adun [ 18/Dec/17 ] |
|
something missed, please replace: 3. run command, such as:
to: 3. run command, such as:
|