[jira] [Resolved] (IMPALA-6159) DataStreamSender should transparently handle some connection reset by peer

["Thomas Tauber-Marshall (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Tauber-Marshall resolved IMPALA-6159.
--------------------------------------------
    Fix Version/s: Impala 3.3.0
       Resolution: Fixed

> DataStreamSender should transparently handle some connection reset by peer
> --------------------------------------------------------------------------
>
>                 Key: IMPALA-6159
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6159
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Distributed Exec
>    Affects Versions: Impala 2.12.0
>            Reporter: Michael Ho
>            Assignee: Michael Ho
>            Priority: Critical
>             Fix For: Impala 3.3.0
>
>
> A client to server KRPC connection can become stale if the socket was closed on the server side due to various reasons such as idle connection removal or remote Impalad restart. Currently, the KRPC code will invoke the callback of all RPCs using that stale connection with the failed status (e.g. "Connection reset by peer"). DataStreamSender should pattern match against certain error string (as they are mostly output from strerror()) and retry the RPC transparently. This may be also be useful for KUDU-2192 which tracks the effort to detect stuck connection and close them. In which case, we may also want to transparently retry the RPC
> FWIW, KUDU-279 is tracking the effort to have a cleaner protocol for connection teardown due to idle client connection removal on the server side. However, Impala still needs to handle other reasons for a stale connection.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)