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

Don't use 30 second network timeout on commands sent to shards through the ShardRegistry

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.6, 3.3.5
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Sharding 13 (04/22/16)

      Description

      In 3.2 we run many commands through the ShardRegistry, instead of using DBClient directly. We wanted to always use a 30 second timeout for all commands sent to the config servers through the ShardRegistry, but in doing so we accidentally started using the 30 second timeout for commands run against shards as well, where it may not be right to do so.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: