You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Harel Ben Attia (JIRA)" <ji...@apache.org> on 2013/11/19 16:15:22 UTC
[jira] [Updated] (HIVE-5853) Hive Lock Manager leaks zookeeper
connections
[ https://issues.apache.org/jira/browse/HIVE-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harel Ben Attia updated HIVE-5853:
----------------------------------
Description:
Hive 0.10 leaks zookeeper connections from ZooKeeperHiveLockManager. HIVE-3723 describes a similar issue for cases of semantic errors and failures, but we're experiencing a consistent connection leak per query (even simple successful queries like "select * from dual").
Workaround: When turning off hive.support.concurrency, everything works fine - no leak (obviously, since the lock manager is not used).
Details:
OS: CentOS 5.9
Hive version: hive-server-0.10.0+67-1.cdh4.2.0.p0.10.el5 and hive-0.10.0+198-1.cdh4.4.0.p0.15.el5
Hadoop version: CDH4.2
Namenode uses HA. Hive's zookeeper configuration uses the NN zookeeper.
The problem occurs both when using the python thrift API, and the java thrift API.
The leak happens even when we're running repeated "select * from dual" queries. We've checked the zookeeper connections using "netstat -n | grep 2181 | grep ESTAB | wc -l".
Eventually, the connection from the client reach the max connections per client limit in ZK, causing new queries to get stuck and never return.
We'll gladly provide more information if needed.
was:
Hive 0.10 leaks zookeeper connections from ZooKeeperHiveLockManager. HIVE-3723 describes a similar issue for cases of semantic errors and failures, but we're experiencing a consistent connection leak per query (even simple successful queries like "select * from dual".
OS: CentOS 5.9
Hive version: hive-server-0.10.0+67-1.cdh4.2.0.p0.10.el5 and hive-0.10.0+198-1.cdh4.4.0.p0.15.el5
Hadoop version: CDH4.2
Namenode uses HA. Hive's zookeeper configuration uses the NN zookeeper.
The problem occurs both when using the python thrift API, and the java thrift API.
The leak happens even when we're running repeated "select * from dual" queries. We've checked the zookeeper connections using "netstat -n | grep 2181 | grep ESTAB | wc -l".
Eventually, the connection from the client reach the max connections per client limit in ZK, causing new queries to get stuck and never return.
We'll gladly provide more infromation if needed.
> Hive Lock Manager leaks zookeeper connections
> ---------------------------------------------
>
> Key: HIVE-5853
> URL: https://issues.apache.org/jira/browse/HIVE-5853
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Harel Ben Attia
>
> Hive 0.10 leaks zookeeper connections from ZooKeeperHiveLockManager. HIVE-3723 describes a similar issue for cases of semantic errors and failures, but we're experiencing a consistent connection leak per query (even simple successful queries like "select * from dual").
> Workaround: When turning off hive.support.concurrency, everything works fine - no leak (obviously, since the lock manager is not used).
> Details:
> OS: CentOS 5.9
> Hive version: hive-server-0.10.0+67-1.cdh4.2.0.p0.10.el5 and hive-0.10.0+198-1.cdh4.4.0.p0.15.el5
> Hadoop version: CDH4.2
> Namenode uses HA. Hive's zookeeper configuration uses the NN zookeeper.
> The problem occurs both when using the python thrift API, and the java thrift API.
> The leak happens even when we're running repeated "select * from dual" queries. We've checked the zookeeper connections using "netstat -n | grep 2181 | grep ESTAB | wc -l".
> Eventually, the connection from the client reach the max connections per client limit in ZK, causing new queries to get stuck and never return.
> We'll gladly provide more information if needed.
--
This message was sent by Atlassian JIRA
(v6.1#6144)