[SERVER-38438] Separate HostUnresponsive from HostUnreachable Created: 06/Dec/18  Updated: 08/Jan/24  Resolved: 24/Jan/19

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Backlog - Service Architecture
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-37389 Give different messages for different... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

So as is, we mark both econnreset and enetreset as the same HostUnreachable. It came up in discussion with mira.carey@mongodb.com that perhaps we want to separate the error code to HostUnreachable and something like HostUnresponsive so as to differentiate what we believe are network failures versus mongod failures.



 Comments   
Comment by Mira Carey [ 24/Jan/19 ]

After some consideration, I don't think we have use cases in mind for programatically pivoting off these different kinds of errors (so separate error codes aren't really warranted)

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