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

ShardRegistry should mark hosts which failed due to OperationTimeout as faulty

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.2.4, 3.3.2
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • Sharding 10 (02/19/16)

      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.

            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: