Separate HostUnresponsive from HostUnreachable

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Networking
    • None
    • Service Arch
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: