[
https://issues.apache.org/jira/browse/HIVE-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305471#comment-14305471
]
Anubhav Agarwal commented on HIVE-7069:
---------------------------------------
We are having the same issue with hive2 jdbc connection on CDH 5.3 which comes
with 0.13.1. If we keep hive concurrency on then simple select statement create
a zookeeper connection that is never closed. We open the hive2 jdbc connection
then run a number of select queries that in turn create a zookeeper connection
for each of them. We never explicitly call zookeeper in our code. So, is there
a way to force close zookeeper connection in this case? Any help would be
appreciated.
> Zookeeper connection leak
> -------------------------
>
> Key: HIVE-7069
> URL: https://issues.apache.org/jira/browse/HIVE-7069
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.12.0
> Environment: Linux 2.6.32-431.11.2.el6.x86_64 #1 SMP Tue Mar 25
> 19:59:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Zilvinas Saltys
>
> We're using CDH 5.0.0 which ships with HIVE 0.12.0. We're running HiveServer2
> and connect to it via JDBC. We have zookeeper support enabled. If a
> connection is made to HS2 and not explicitly closed via JDBC then a
> connection made to zookeeper is never released. It reaches a point where HS2
> hangs and stops executing any new queries. It's easy to replicate with a
> simple script that connects to HS2 via JDBC and runs a simple query like
> 'show tables'. At the same time run this on the hive server machine to
> monitor zookeeper connections: 'while sleep 1; do netstat -anlp | grep 2181 |
> wc -l; done' .. If you close the connection explicitly the count will go down
> soon after the program exits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
