[SERVER-2431] mongos throws an uncaught socket exception when it can't reach the config server Created: 29/Jan/11 Updated: 12/Jul/16 Resolved: 06/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.7.6 |
| Fix Version/s: | 2.4.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux x86_64 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Repro steps: Start mongos with the --configdb parameter referring to a mongod that doesn't exist: Fri Jan 28 17:51:17 mongos db version v1.8.0-rc0-pre-, pdfile version 4.5 starting (--help for usage) I can also reproduce this by passing a configdb that hasn't completely settled down yet. Logging mongos to a file you can see something like this: Fri Jan 28 17:41:26 mongos db version v1.8.0-rc0-pre-, pdfile version 4.5 starting (--help for usage) |
| Comments |
| Comment by Greg Studer [ 06/Mar/14 ] |
|
Pretty sure this was fixed as part of other general config upgrade changes. |