[SERVER-20318] Retry on failed reads from CSRS config servers Created: 08/Sep/15  Updated: 25/Jan/17  Resolved: 28/Sep/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.1.7
Fix Version/s: 3.1.9

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-20082 Add maxTimeMs to config catalog opera... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding A (10/09/15)
Participants:

 Description   

When a read to a config server fails due to connectivity issues, the catalogManager does not attempt to try again on another potentially available node. This is a regression compared to the legacy SyncCluster behavior where it keeps on going through the list of config servers.



 Comments   
Comment by Githook User [ 28/Sep/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-20318 Retry on failed reads from CSRS config servers
Branch: master
https://github.com/mongodb/mongo/commit/f3b366d65273a00061b235804e7e149d407f7c4e

Comment by Githook User [ 28/Sep/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-20318 Allow NetworkTestEnv::OnCommand to set non ok status to response
Branch: master
https://github.com/mongodb/mongo/commit/22b72fe112bc3e1c098e4404032d6471b5858773

Comment by Githook User [ 28/Sep/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-20318 Consolidate all read helpers in CatalogManagerReplicaSet and make them responsible for targetting
Branch: master
https://github.com/mongodb/mongo/commit/66a6aef744e9e779fbd33569415ce5b68ede413c

Generated at Thu Feb 08 03:53:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.