[SERVER-4076] when migration fails due to conn error, no response sent Created: 15/Oct/11 Updated: 11/Jul/16 Resolved: 12/Dec/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.0 |
| 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 | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
When a connectivity error occurs between mongod hosts during a migrate, no error is returned to the client (mongos), and apparently the socket is reset. This should probably be caught and rethrown as a more informative error which can then be reported in mongos logs. |
| Comments |
| Comment by auto [ 12/Dec/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: more informative error messages on network failure during migration also prevents calling socket from being closed, which is unnecessary |