Stop converting SocketException to HostUnreachable in NITL

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • N&O 2026-07-20, N&O 2026-08-03
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      NITL converts SocketException to HostUnreachable, apparently due to legacy sharding SDAM logic according to the comment there:

      // The TransportLayer has, for historical reasons returned SocketException for network
      // errors, but sharding assumes HostUnreachable on network errors.

      However, this is no longer true. Remote command targeting / SDAM error handling uses error categories such as NetworkError (which HostUnreachable belongs to) to make these changes:

      We should remove this conversion logic as it is no longer needed and can obfuscate the intended error codes returned from the TransportLayer.

            Assignee:
            Samuel Goodrick
            Reporter:
            Patrick Freed
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: