-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Networking
-
None
-
Service Arch
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.
- is related to
-
SERVER-37389 Give different messages for different connection failure reasons
- Closed