[
https://issues.apache.org/jira/browse/HBASE-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
punwinger updated HBASE-13437:
------------------------------
Description: HBase ThriftServer will cache Zookeeper connection in memory
using org.apache.hadoop.hbase.util.ConnectionCache. This class has a mechanism
called chore to clean up connections idle for too long(default is 10 min). But
method timedOut for testing whether idle exceed for maxIdleTime always return
false which leads to never release the Zookeeper connection. If we send request
to ThriftServer every maxIdleTime then ThriftServer will keep thousands of
Zookeeper Connection soon. (was: HBase ThriftServer will cache Zookeeper
connection in memory using org.apache.hadoop.hbase.util.ConnectionCache. This
class has a mechanism called chore to clean up connections idle for too
long(default is 10 min). But method timedOut for testing whether idle exceed
for maxIdleTime always return false which leads to never release the Zookeeper
connection. If we send requestto ThriftServer every maxIdleTime then
ThriftServer will keep thousands of Zookeeper Connection soon.)
> ThriftServer leaks ZooKeeper connections
> ----------------------------------------
>
> Key: HBASE-13437
> URL: https://issues.apache.org/jira/browse/HBASE-13437
> Project: HBase
> Issue Type: Bug
> Components: Thrift
> Affects Versions: 0.98.8
> Reporter: punwinger
>
> HBase ThriftServer will cache Zookeeper connection in memory using
> org.apache.hadoop.hbase.util.ConnectionCache. This class has a mechanism
> called chore to clean up connections idle for too long(default is 10 min).
> But method timedOut for testing whether idle exceed for maxIdleTime always
> return false which leads to never release the Zookeeper connection. If we
> send request to ThriftServer every maxIdleTime then ThriftServer will keep
> thousands of Zookeeper Connection soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
