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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.4.0-rc2
    • Fix Version/s: 3.4.0-rc4
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2016-11-21
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

          related to

          Task - A task that needs to be done. SERVER-29438 Combine max_time_ms_sharded_new_commands.js with max_time_ms_sharded.js

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Open

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: