[
https://issues.apache.org/jira/browse/HBASE-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507435#comment-14507435
]
Hudson commented on HBASE-13437:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6401 (See
[https://builds.apache.org/job/HBase-TRUNK/6401/])
HBASE-13437 ThriftServer leaks ZooKeeper connections (Winger Pun) (tedyu: rev
2bf8cda4f68940909e9bcfdf8ae41cc751a49c7d)
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/ConnectionCache.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestConnectionCache.java
> 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: Winger Pun
> Fix For: 2.0.0, 1.1.0, 0.98.13, 1.0.2, 1.2.0
>
> 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)
