[SERVER-59142] Add dropConnections API to TaskExecutor Created: 05/Aug/21  Updated: 29/Oct/23  Resolved: 22/Oct/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Task Priority: Major - P3
Reporter: George Wangensteen Assignee: Vojislav Stojkovic
Resolution: Fixed Votes: 0
Labels: save-for-vojislav, servicearch-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-36417 Drop pooled connections to nodes no l... Blocked
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2021-10-04, Service Arch 2021-11-01
Participants:
Story Points: 2

 Description   

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



 Comments   
Comment by Githook User [ 21/Oct/21 ]

Author:

{'name': 'Vojislav Stojkovic', 'email': 'vojislav.stojkovic@mongodb.com', 'username': 'vstojkovic-mongodb'}

Message: SERVER-59142 Add dropConnections API to TaskExecutor
Branch: master
https://github.com/mongodb/mongo/commit/e5db84f4b341fbd8723ca36b16f961284261e00f

Generated at Thu Feb 08 05:46:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.