[SERVER-36415] Add dropConnections(const HostAndPort&) to the EgressTagCloser Created: 02/Aug/18 Updated: 29/Oct/23 Resolved: 13/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Jonathan Ma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Service Arch 2018-12-17 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The egress tag closing machinery should provide a way to drop pooled connections to a particular host and port. This should plumb down to ConnectionPool::dropConnections(const HostAndPort&) |
| Comments |
| Comment by Githook User [ 11/Dec/18 ] |
|
Author: {'name': 'Jonathan', 'email': 'thejonathanma@gmail.com', 'username': 'thejonathanma'}Message: |
| Comment by Benjamin Caimano (Inactive) [ 04/Dec/18 ] |
|
jonathan.ma, so our default connection pool is an EgressTagCloser. However, we don't have a HostAndPort function in the EgressTagCloserManager. The plumbing should be relatively straightforward. We'd probably want to expand testing around here. |