[SERVER-46331] Check for SocketException error on response object in NetworkInterfaceTL Created: 21/Feb/20 Updated: 29/Oct/23 Resolved: 26/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.3 Required |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2020-02-24, Sharding 2020-03-09 | ||||
| Participants: | |||||
| Linked BF Score: | 49 | ||||
| Description |
|
We recently moved some code around that converted a SocketException to a HostUnreachable error in NetworkInterfaceTL. We don't enter the onError function where we now do this check and switch in this case however, because it's wrapped response object itself that has this error rather than the status wrapping it. |
| Comments |
| Comment by Githook User [ 25/Feb/20 ] |
|
Author: {'name': 'Janna Golden', 'username': 'jannaerin', 'email': 'janna.golden@mongodb.com'}Message: |