[SERVER-73609] Let PinnedConnectionTaskExecutor acquire transport connections from the NetworkInterface it uses Created: 03/Feb/23  Updated: 14/Apr/23  Resolved: 31/Mar/23

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

Type: Task Priority: Major - P3
Reporter: George Wangensteen Assignee: Backlog - Service Architecture
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-73608 Create skeleton for PinnedConnectionT... Closed
depends on SERVER-73610 Introduce connection-leasing from Con... Closed
is depended on by SERVER-73611 Implement RPC functionality of Pinned... Closed
Duplicate
duplicates SERVER-73611 Implement RPC functionality of Pinned... Closed
Assigned Teams:
Service Arch
Backport Requested:
v6.3
Participants:

 Description   

Ensure that PinnedConnectionTaskExecutor can lease out transport connections from the NetworkInterfaceTL it wraps/uses. This may involve letting it access the NetworkInterface of the underlying task executor via a getter or friendship, or by adding direct connection-acquisition ability to the wrapped TaskExecutor's API. 



 Comments   
Comment by George Wangensteen [ 31/Mar/23 ]

Done as part of SERVER-73611 and SERVER-73610

Generated at Thu Feb 08 06:25:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.