Avoid dropping pools for any error thrown during connection setup

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0, 6.0.7
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • ALL
    • v6.0
    • Service Arch 2022-09-05, Service Arch 2022-09-19, Service Arch 2022-10-03
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently convert all errors encountered during connection-setup to HostUnreachable, which causes the connection-pool to tag the target host as unhealthy and drop all connections (see below for more details). This behavior is not correct for all errors (e.g., EINPROGRESS) and the error-handling code should be adjusted accordingly. A possible solution is to only drop connections for a specific group of errors that are a clear indication that the target host is unhealthy.

      Here is the path through which we convert all connection setup errors to HostUnreachable:

              Assignee:
              Alex Li
              Reporter:
              Amirsaman Memaripour
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: