[SERVER-7862] Connection timeouts in mongos Created: 06/Dec/12 Updated: 06/Dec/22 Resolved: 19/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dmitry Prokoptsev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Although DBClient* family classes support custom socket timeouts, mongos does not specify any. This can lead to hung queries in cases if mongos is running locally but mongod is running on remote host and a major networking issue takes place. |
| Comments |
| Comment by Matt Kangas [ 26/Jun/14 ] |
|
We believe that implementing a connection-level timeout today will mask other problems and and can lead to systemic retry issues. The solution we are working towards is operation-level timeouts within mongos. Linking to a related issue |
| Comment by Pavlo Grinchenko [ 30/Jul/13 ] |
|
We might need this as well - in our case we see intermittent timeouts when mongodump is doing backups. |
| Comment by Dmitry Prokoptsev [ 06/Dec/12 ] |
|
I've created a patch ( https://github.com/mongodb/mongo/pull/335 ) which solves the issue. Hope it is useful. |