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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.4, 3.3.2
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      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

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

                Dates

                • Created:
                  Updated:
                  Resolved: