You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2025/01/16 17:44:00 UTC

[jira] [Resolved] (IMPALA-13253) Add option to use TCP keepalives for client connections

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

Joe McDonnell resolved IMPALA-13253.
------------------------------------
    Fix Version/s: Impala 4.5.0
         Assignee: Joe McDonnell
       Resolution: Fixed

> Add option to use TCP keepalives for client connections
> -------------------------------------------------------
>
>                 Key: IMPALA-13253
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13253
>             Project: IMPALA
>          Issue Type: Task
>          Components: Backend, Clients
>    Affects Versions: Impala 4.5.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Blocker
>             Fix For: Impala 4.5.0
>
>
> A client can be disconnected without explicitly closing its TCP connection. This can happen if the client machine resets or there is a network disruption. In particular, load balancers can have an idle time that results in a connection becoming invalid. Impala can't really guarantee that the client will properly tear down its connection and the Impala side resources will be released.
> TCP keepalive would allow Impala to detect dead clients and close the connection. It also can prevent a load balancer from seeing the connection as idle. This can be important for clients that hold connections in a pool.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)