[
https://issues.apache.org/jira/browse/IMPALA-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868420#comment-17868420
]
Joe McDonnell commented on IMPALA-13183:
----------------------------------------
Here is an AWS blog post about how the AWS LB works:
[https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-configurable-idle-timeout-for-connection-tracking/]
The section about "Scenario #1: TCP connections through AWS Services" explains
that it doesn't send packets when a connection goes idle. An endpoint would
only find out when it sends a message. I think this is a problem for Impala,
and having an idle connection timeout would be one way to avoid issues.
> Add default timeout for hs2/beeswax server sockets
> --------------------------------------------------
>
> Key: IMPALA-13183
> URL: https://issues.apache.org/jira/browse/IMPALA-13183
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Csaba Ringhofer
> Priority: Major
>
> Currently Impala only sets timeout for specific operations, for example
> during SASL handshake and when checking if connection can be closed due to
> idle session.
> https://github.com/apache/impala/blob/d39596f6fb7da54c24d02523c4691e6b1973857b/be/src/rpc/TAcceptQueueServer.cpp#L153
> https://github.com/apache/impala/blob/d39596f6fb7da54c24d02523c4691e6b1973857b/be/src/transport/TSaslServerTransport.cpp#L145
> There are several cases where an inactive client could keep the connection
> open indefinitely, for example if it hasn't opened a session yet.
> I think that there should be a general longer timeout set for both send/recv,
> e.g. flag client_default_timout_s=3600.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
