hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13437) ThriftServer leaks ZooKeeper connections
Date Mon, 13 Apr 2015 17:56:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492742#comment-14492742

Nick Dimiduk commented on HBASE-13437:

Okay, yes. Makes sense. +1.

We have no test coverage for connection expiration?

> 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
>         Attachments: 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

View raw message