[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:
Related
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 SERVER-4076

also prevents calling socket from being closed, which is unnecessary
Branch: master
https://github.com/mongodb/mongo/commit/e1439a3740b3fdf67b7414b013d48f58fd1b4532

Generated at Thu Feb 08 03:04:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.