[SERVER-6313] config server timeouts not used in all places Created: 05/Jul/12  Updated: 11/Jul/16  Resolved: 11/Dec/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.3.2

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

Issue Links:
Related
related to SERVER-6178 Cannot use mongos if subset of config... Closed
Operating System: ALL
Participants:

 Description   

In some cases when connecting to the config server we do not use a timeout - this can lead to hangs when the config server is totally unresponsive. We add timeouts to all config server interactions and make sure we handle correctly when timeouts fail.



 Comments   
Comment by auto [ 11/Dec/12 ]

Author:

{u'date': u'2012-12-04T21:51:29Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}

Message: SERVER-6313 config server timeouts not used in all places
Branch: master
https://github.com/mongodb/mongo/commit/29ce113eac4a3bc9560e6f19160953895b4aff95

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