[SERVER-3220] mongos hangs waiting for downed config server Created: 08/Jun/11 Updated: 12/Jul/16 Resolved: 14/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.9.0 |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
If a config server doesn't respond, mongos hangs waiting for the connection. To reproduce, drop incoming config server packets from one of three config servers: sudo /sbin/iptables -A INPUT -i eth0 -p tcp -m tcp --dport THE_LISTEN_PORT -j DROP and start a new mongos instance pointed at these servers, should hang. Killing the config server entirely allows mongos to start. |
| Comments |
| Comment by Greg Studer [ 14/Jun/11 ] |
|
master now has the ability to add socket timeouts to scopedDbconnections, now must choose good defaults |
| Comment by Greg Studer [ 08/Jun/11 ] |
|
patch in review |