[
https://issues.apache.org/jira/browse/IMPALA-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021248#comment-18021248
]
Michael Smith commented on IMPALA-14440:
----------------------------------------
According to
https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-nlb-tcp-configurable-idle-timeout/
NLB defaults to 350s for TCP connections. Most services I've found tend to use
<=120s for HTTP, <=350s for TCP; however Azure doesn't seem to make a
distinction and starts at 4 minutes. So I'm in favor of 300s or 360s as a safe
default.
> Provide non-zero default for http_socket_timeout_s
> --------------------------------------------------
>
> Key: IMPALA-14440
> URL: https://issues.apache.org/jira/browse/IMPALA-14440
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Reporter: Michael Smith
> Priority: Major
>
> impala-shell's {{http_socket_timeout_s}} option configures the HTTP client
> for HS2-HTTP connections to have a timeout, so it doesn't hang indefinitely
> on a failed connection. When it times out, the client may then retry.
> We should consider adding a non-zero default value for this setting to avoid
> hung clients with HS2-HTTP in very busy environments.
> IMPALA-11126 added this option but left it disabled by default to avoid
> impacting existing behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
