[SERVER-73608] Create skeleton for PinnedConnectionTaskExecutor Created: 03/Feb/23  Updated: 29/Oct/23  Resolved: 15/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 6.0.6

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

Issue Links:
Backports
Depends
is depended on by SERVER-73609 Let PinnedConnectionTaskExecutor acqu... Closed
Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.3
Sprint: Service Arch 2023-02-20
Participants:

 Description   

Create a skeleton for a new type of TaskExecutor that uses a single transport connection for all RPC scheduled through it. This task executor should own another TaskExecutor and implement most of the TaskExecutor API by dispatching to the owned TaskExecutor. It should leave the RPC portions of the API (scheduleRemoteCommandOnAny) unimplemented to be filled out later. The eventual implementation will acquire a unique connection from the NetworkInterface owned by this task executor when the first RPC is scheduled, and use that connection for all future RPCs for the lifetime of the PinnedConnectionTaskExecutor. 


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