[
https://issues.apache.org/jira/browse/IMPALA-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Smith resolved IMPALA-14674.
------------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Support connect_timeout_ms for HS2-HTTP
> ---------------------------------------
>
> Key: IMPALA-14674
> URL: https://issues.apache.org/jira/browse/IMPALA-14674
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> HS2-HTTP has not previously implemented {{connect_timeout_ms}} to time out
> connections that have been closed or became unavailable (like a node
> disappearing from a load balancer) because of concerns around the HS2-HTTP
> client closing and re-opening connections frequently on a bad endpoint. That
> also resulted in a warning whenever using HS2-HTTP of
> {code}
> Warning: --connect_timeout_ms is currently ignored with HTTP transport.
> {code}
> IMPALA-14460 addresses some of that concern by re-using the connection if
> available and retrying closed connections only under specific circumstances.
> {{http_socket_timeout_ms}} was added to provide an alternative, but it
> applies to the whole HTTP request. Long-running requests - like
> ExecuteStatement when planning is very involved - would require a longer
> timeout, so setting a default is challenging. In some environments, it may
> still make sense to set a default matching the lifetime of load balancer
> timeouts, but those will vary by environment. Also see IMPALA-14440.
> We should support {{connect_timeout_ms}} only for the portion of the HS2-HTTP
> protocol where a socket connection is established, and use
> {{http_socket_timeout_ms}} for the remainder of the session when sending HTTP
> requests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
