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

Sharding host targeting logic should use the remaining time from the OperationContext as a timeout

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Service Arch 2019-02-11

    Description

      Currently RemoteCommandTargeter::selectFindHostMaxWaitTime() will always return a default timeout:

      https://github.com/mongodb/mongo/blob/master/src/mongo/client/remote_command_targeter.cpp#L48-L49

      This is the timeout which we use when targeting a particular host within a shard. Instead of using a default, we should attach a timeout to the OperationContext (potentially the maxTimeMS value) and use this as the host targeting timeout.

      Attachments

        Activity

          People

            mathias@mongodb.com Mathias Stearn
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: