[SERVER-8648] checkStatus in DBClientReplicaSet has no explicit socket timeout Created: 21/Feb/13 Updated: 11/Jul/16 Resolved: 21/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.4, 2.4.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | Blackhole a connection from mongos to a replica set primary - the monitor hangs. |
||||
| Participants: | |||||
| Description |
|
...this is bad since we hold a lock which prevents other connection checks until the replSetGetStatus returns. Other timeouts for the ReplicaSetMonitors are aggressively set to 5s, we should probably do this here. |
| Comments |
| Comment by auto [ 18/Mar/13 ] |
|
Author: {u'date': u'2013-03-18T14:28:44Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Revert "Revert " also |
| Comment by Daniel Pasette (Inactive) [ 14/Mar/13 ] |
|
reverting in 2.2 branch while investigation of |
| Comment by auto [ 14/Mar/13 ] |
|
Author: {u'date': u'2013-03-14T21:12:14Z', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: Revert " This reverts commit 294c08491709b8fffae0ed1b63b8c34b35f9621a. |
| Comment by auto [ 21/Feb/13 ] |
|
Author: {u'date': u'2013-02-21T06:23:48Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 21/Feb/13 ] |
|
Author: {u'date': u'2013-02-21T06:23:48Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |