The TaskExecutor is already Network-Interface aware, and can gather stats about connections maintained by its NITL as well as schedule requests to a server residing at a specific HostAndPort. Sometimes, users of the TaskExecutor might want to drop connections to a specific host and port; we should allow them to do so. The underlying ThreadPoolTaskExecutor type already provides this functionality, so we should just add a declaration to the TaskExecutor interface, provide an implementation for ShardingTaskExecutor that just dispatches to the underlying ThreadPoolTaskExecutor it wraps, and provide an appropriate implementation to the unittest proxy