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

Thiruvel Thirumoolan commented on HIVE-5268:
--------------------------------------------

Thanks for raising this Vaibhav. We have a similar patch which cleans up 
session related info when network issues cause client disconnection or clients 
fail to close sessions. The patch is available for Hive-11 and am porting that 
to Hive12 and trunk. Unfortunately I didnt create the JIRA earlier. The patch 
cleanups aggressively as soon as the client disconnects. Based on Carl's 
feedback from a hive meetup, we would like to have a session timeout after 
which all idle/disconnected sessions are cleaned. I was working towards that.

Have you started working on this? If not, can I start by uploading the 
aggressive patch I have and then go forward with the improvements?
                
> 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

Reply via email to