[
https://issues.apache.org/jira/browse/HBASE-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985473#comment-14985473
]
Pawel Kucharski commented on HBASE-13437:
-----------------------------------------
workaround is to disable HTablePoll by
{code:xml}
<property>
<name>hbase.thrift.htablepool.size.max</name>
<value>0</value>
</property>
{code}
> 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: Winger Pun
> Assignee: Albert Strasheim
> Fix For: 2.0.0, 1.1.0, 0.98.13, 1.0.2
>
> Attachments: HBASE-13437_1.patch, HBASE-13437_1.patch,
> hbase-13437-fix.patch
>
>
> 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)
