You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Stefan Seelmann (JIRA)" <ji...@apache.org> on 2011/09/15 23:59:09 UTC
[jira] [Updated] (HBASE-4417) HBaseAdmin.checkHBaseAvailable()
doesn't close ZooKeeper connections
[ https://issues.apache.org/jira/browse/HBASE-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seelmann updated HBASE-4417:
-----------------------------------
Attachment: HBASE-4417-0.92.diff
HBASE-4417-0.90.diff
Patches for 0.90 (branch) and 0.92 (trunk).
When running the testcase included in the patch without the patched HBaseAdmin class a "netstat | grep 21818 | grep ESTABLISHED" shows that ZooKeeper connections are not closed. Additionally the 1000 time loop opens too many ZooKeeper connections that the test fails.
> HBaseAdmin.checkHBaseAvailable() doesn't close ZooKeeper connections
> --------------------------------------------------------------------
>
> Key: HBASE-4417
> URL: https://issues.apache.org/jira/browse/HBASE-4417
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.90.4, 0.92.0
> Reporter: Stefan Seelmann
> Priority: Minor
> Fix For: 0.92.0, 0.90.5
>
> Attachments: HBASE-4417-0.90.diff, HBASE-4417-0.92.diff
>
>
> HBaseAdmin.checkHBaseAvailable(conf) clones the passed connection, later in HBaseAdmin constructor the connection is cloned again. Thus a new HConnection object with ZooKeeper connections is created.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira