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

ShardRemote _runCommand does not include the actual operation timeout as part of the command

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.0-rc4
    • Affects Version/s: 3.4.0-rc2
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2016-11-21
    • 0

      The ShardRemote::_runCommand call, which is used by all code paths which need to send a request to the config server or the shards does not include the remainder of the operation as part of the command. This means that for the cases where we do not override the maxTimeMS of a call it will end up using infinite maxTimeMS.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: