[SERVER-43302] Lower default value for ldapConnectionPoolMaximumConnectionsInProgressPerHost Created: 12/Sep/19 Updated: 29/Oct/23 Resolved: 30/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jonathan Reams | Assignee: | Adam Cooper (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 2019-10-07 | ||||||||
| Participants: | |||||||||
| Description |
|
This setParameter controls the maximum number of connections in progress to each ldap server in the connection pool. For slow servers, setting a high value may cause a connection storm to slower ldap servers. We should probably set this to the default for the connection pool of 2. |
| Comments |
| Comment by Githook User [ 30/Sep/19 ] |
|
Author: {'username': 'super-cooper', 'email': 'adam.cooper@mongodb.com', 'name': 'Adam Cooper'}Message: |