[
https://issues.apache.org/jira/browse/HIVE-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778122#comment-13778122
]
Vaibhav Gumashta commented on HIVE-5268:
----------------------------------------
Thanks [~thiruvel]! I haven't started yet and if you post your progress so far,
it would be great. What are your thoughts on session timeout? You might want to
take a look at [HIVE-5217|https://issues.apache.org/jira/browse/HIVE-5217]
which I was thinking of piggybacking on to detect timeouts, but I haven't given
a lot of thought to it.
> HiveServer2 accumulates orphaned OperationHandle objects when a client fails
> while executing query
> --------------------------------------------------------------------------------------------------
>
> Key: HIVE-5268
> URL: https://issues.apache.org/jira/browse/HIVE-5268
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Fix For: 0.13.0
>
>
> When queries are executed against the HiveServer2 an OperationHandle object
> is stored in the OperationManager.handleToOperation HashMap. Currently its
> the duty of the JDBC client to explicitly close to cleanup the entry in the
> map. But if the client fails to close the statement then the OperationHandle
> object is never cleaned up and gets accumulated in the server.
> This can potentially cause OOM on the server over time. This also can be used
> as a loophole by a malicious client to bring down the Hive server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
