[ https://issues.apache.org/jira/browse/HIVE-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504297#comment-13504297 ]
Gunther Hagleitner commented on HIVE-3723: ------------------------------------------ The releaseLocks call happens at various places in the run method. I think that's fine too, since calling destroy would kill the HiveLockManager which is shared between different context objects (i.e.: That should only happen when someone specifically destroys the driver.) As a side note, compile doesn't seem to acquire any locks - the call is thus just a protection against future versions that could. > Hive Driver leaks ZooKeeper connections > --------------------------------------- > > Key: HIVE-3723 > URL: https://issues.apache.org/jira/browse/HIVE-3723 > Project: Hive > Issue Type: Bug > Reporter: Gunther Hagleitner > Assignee: Gunther Hagleitner > Attachments: HIVE-3723.1-r1411423.patch > > > In certain error cases (i.e.: statement fails to compile, semantic errors) > the hive driver leaks zookeeper connections. > This can be seen in the TestNegativeCliDriver test which accumulates a large > number of open file handles and fails if the max allowed number of file > handles isn't at least 2048. -- 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