[
https://issues.apache.org/jira/browse/HIVE-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823831#comment-13823831
]
Thejas M Nair commented on HIVE-5799:
-------------------------------------
I think this patch certainly improves over what we have right now. But with
this approach, the timeout has to be set to a long value (couple of days?), to
be fairly certain that the user does not expect the session to be still around.
We won't know if the user application is still up and running.
A better approach would be to send heartbeats from the client to server with
the session handle, that way we don't have to wait too long before considering
the client to be dead and closing the session.
> session/operation timeout for hiveserver2
> -----------------------------------------
>
> Key: HIVE-5799
> URL: https://issues.apache.org/jira/browse/HIVE-5799
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: HIVE-5799.1.patch.txt, HIVE-5799.2.patch.txt
>
>
> Need some timeout facility for preventing resource leakages from instable or
> bad clients.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
