Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
4.0.0
-
None
Description
When hiveserver2 is behind multiple proxies there is possibility of "broken pipe", "connect timeout" and "read timeout" exceptions if one of the intermediate proxies or load balancers decided to reset the underlying tcp socket after idle timeout. When the connection is broken and when the query is submitted after idle timeout from beeline (or client) perspective the connection is open but http methods (POST/GET) fails with socket related exceptions. Since these methods are not sent to the server these are safe for client side retries.
Also HIVE-12371 seems to apply the socket timeout only to binary transport. Same can be passed on to http client as well to avoid retry hang issues with infinite timeouts.
Attachments
Issue Links
- Is contained by
-
HIVE-26751 Bug Fixes and Improvements for 3.2.0 release
- Open
- relates to
-
HIVE-25203 HiveQueryResultSet and client operation are not expected to be closed twice
- Closed
-
HIVE-25509 CLIService.closeOperation should not fail if operation handle is not present
- Closed
- links to