[SERVER-38926] ConnectionPool runs ConnectionInterface actions asynchronously Created: 10/Jan/19 Updated: 15/Jan/19 Resolved: 15/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | Service Arch 2019-01-14, Service Arch 2019-01-28 | ||||
| Participants: | |||||
| Description |
|
spawnConnections() loops until target is achieved. In the case where we cannot make new connections for whatever reason, this will loop forever. |
| Comments |
| Comment by Benjamin Caimano (Inactive) [ 15/Jan/19 ] |
|
As tempting as it is to re-purpose this ticket to make the connection pooling promises clearer, we're kicking off this sort of work for a planned connection pool rewrite. |
| Comment by Benjamin Caimano (Inactive) [ 10/Jan/19 ] |
|
Marking as v4.0 backported with a caveat that it may end up declined. |