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

ShardRegistry should mark hosts which failed due to OperationTimeout as faulty

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.2.4, 3.3.2
    • Sharding
    • Fully Compatible
    • ALL
    • Sharding 10 (02/19/16)

    Description

      The shard ShardRegistry should mark hosts which failed due to OperationTimeout as faulty in the ReplicaSetMonitor so that they are not being contacted again on a second attempt.

      If the host timed out because of some transient error, it will eventually be put on the online list again and will start being contacted.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: