[SERVER-41828] Ensure LDAP conn pool prefers ldap servers listed first Created: 19/Jun/19 Updated: 29/Oct/23 Resolved: 20/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.11, 4.2.0-rc3, 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jonathan Reams | Assignee: | Jonathan Reams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.2, v4.0
|
||||||||
| Sprint: | Security 2019-07-01 | ||||||||
| Participants: | |||||||||
| Description |
|
The LDAP connection pool currently tries to connect to all servers at once and returns the first one that succeeds. However in the common case where the connection pool has a bunch of healthy connections, this can lead to very non-deterministic host selection. We should try to get a connection to each ldap server in they order they are listed, and only start connecting to them asynchronously if they cannot be fulfilled immediately. |
| Comments |
| Comment by Githook User [ 10/Jul/19 ] |
|
Author: {'name': 'Jonathan Reams', 'username': 'jbreams', 'email': 'jbreams@mongodb.com'}Message: (cherry picked from commit 5d6c438c6967c6bad3d1083e6621aba82d222129) |
| Comment by Githook User [ 08/Jul/19 ] |
|
Author: {'name': 'Jonathan Reams', 'username': 'jbreams', 'email': 'jbreams@mongodb.com'}Message: (cherry picked from commit 5d6c438c6967c6bad3d1083e6621aba82d222129) |
| Comment by Githook User [ 20/Jun/19 ] |
|
Author: {'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}Message: |