[SERVER-45114] Connect AsyncDBClient exhaust functionality throughout Created: 12/Dec/19  Updated: 29/Oct/23  Resolved: 19/Feb/20

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-45109 Modify AsyncDBClient to allow exhaust... Closed
is depended on by SERVER-44951 Expand TaskExecutor to implement sche... Closed
Related
related to SERVER-58310 ThreadPoolTaskExecutor is memory unsa... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2019-12-30, Service Arch 2020-01-13, Service Arch 2020-01-27, Service Arch 2020-02-10, Service Arch 2020-02-24
Participants:

 Description   

The normal chain for a command request goes like this:

  1. Local Request object construction
  2. [ThreadPool]TaskExecutor::scheduleRemoteCommand()
  3. NetworkInterface[TL]::startCommand()
  4. AsyncDBClient::runCommandRequest()

Each layer needs to have be expanded to allow at least a Status-returning callback to process each exhaust message. SERVER-41549 might be a natural consequence of this work.



 Comments   
Comment by Githook User [ 19/Feb/20 ]

Author:

{'username': 'jannaerin', 'name': 'Janna Golden', 'email': 'janna.golden@mongodb.com'}

Message: SERVER-45114 Connect AsyncDBClient exhaust functionality throughout
Branch: master
https://github.com/mongodb/mongo/commit/49643264238b895bd5ec1dfb39597f75a1db60ec

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