[
https://issues.apache.org/jira/browse/HIVE-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amruth S updated HIVE-18497:
----------------------------
Description:
Hive server failures are making the JDBC client get stuck in socketRead.
Users should be able to configure socket read timeout to fail fast in case of
server failures.
*Proposed solution*
Add a Jdbc connection param
*hive.client.read.socket.timeoutmillis*
This can control the socket read timeout, connect timeout in TCP as well as
HTTP mode.
Let me know your thoughts.
was:
Hive server failures are making the JDBC client get stuck in socketRead.
Users should be able to configure socket read timeout to fail fast in case of
server failures.
*Proposed solution*
Add a Jdbc connection param **
*hive.client.read.socket.timeoutmillis*
This can control the socket read timeout, connect timeout in TCP as well as
HTTP mode.
Let me know your thoughts.
> JDBC connection parameter to control socket read timeout
> --------------------------------------------------------
>
> Key: HIVE-18497
> URL: https://issues.apache.org/jira/browse/HIVE-18497
> Project: Hive
> Issue Type: Improvement
> Components: Clients, JDBC
> Reporter: Amruth S
> Priority: Minor
>
> Hive server failures are making the JDBC client get stuck in socketRead.
> Users should be able to configure socket read timeout to fail fast in case of
> server failures.
> *Proposed solution*
> Add a Jdbc connection param
> *hive.client.read.socket.timeoutmillis*
> This can control the socket read timeout, connect timeout in TCP as well as
> HTTP mode.
> Let me know your thoughts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
