Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-45114

Connect AsyncDBClient exhaust functionality throughout

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • 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

      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.

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: