[SERVER-22627] ShardRegistry should mark hosts which failed due to OperationTimeout as faulty Created: 16/Feb/16  Updated: 21/Nov/16  Resolved: 17/Feb/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.2.4, 3.3.2

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-22620 Improve mongos handling of a very sta... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Sharding 10 (02/19/16)
Participants:

 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.



 Comments   
Comment by Githook User [ 17/Feb/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-22627 Mark hosts which failed due to OperationTimeout as faulty
Branch: v3.2
https://github.com/mongodb/mongo/commit/a796aaaf28fd53b54ffb6b01cdcf147447235a34

Comment by Githook User [ 17/Feb/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-22627 Mark hosts which failed due to OperationTimeout as faulty
Branch: master
https://github.com/mongodb/mongo/commit/55bcbd372df4035b1bb7cae9966c066305ed462e

Generated at Thu Feb 08 04:00:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.