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

ARS::next() does not respect OperationContext deadline

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2020-08-24, Security 2021-01-25, Security 2021-02-08, Security 2021-02-22
    • Case:

      Description

      In 4.0, AsyncRequestsSender::next() can end up calling _scheduleRequests, which eventually tries to do shard targeting in a blocking manner. This deadline in shard targeting should be updated to be the minimum of the current deadline and the deadline set on the OperationContext, so that clients aren't accidentally blocked if targeting takes a long time.

      We should also add a deadline to this call to Baton::run.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ben.caimano Benjamin Caimano (Inactive)
              Reporter:
              matthew.saltz Matthew Saltz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: