[jira] [Commented] (HIVE-5268) HiveServer2 accumulates orphaned OperationHandle objects when a client fails while executing query

["Vaibhav Gumashta (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794538#comment-13794538 ] 

Vaibhav Gumashta commented on HIVE-5268:
----------------------------------------

[~thiruvel]: It would be great if you can upload the patch you were mentioning. I was curious about your cleanup the approach. Thanks a lot! 

> 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 was sent by Atlassian JIRA
(v6.1#6144)