[SERVER-71230] Add baton support to async_rpc command senders Created: 09/Nov/22  Updated: 29/Oct/23  Resolved: 04/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

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

Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2022-12-26, Service Arch 2022-11-14, Service Arch 2022-11-28, Service Arch 2022-12-12, Service Arch 2023-01-09
Participants:

 Description   

The overloads of async_rpc::sendCommand and async_rpc::sendHedgedCommand that accept an OperationContext should also optionally accept a baton, in addition to a TaskExecutor. When a baton is provided, it should be used to run continuations that the rpc layer schedules before and after sending a command to the network via TaskExecutor::scheduleRemoteCommand. It should additionally be passed to the lower networking layers so that it can be used for polling if it is a NetworkingBaton. 



 Comments   
Comment by Githook User [ 04/Jan/23 ]

Author:

{'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}

Message: SERVER-71230 Add baton support to async rpc senders
Branch: master
https://github.com/mongodb/mongo/commit/99cf1c7c97eb67ad7505140e20cab9d1c23d0b0c

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