[
https://issues.apache.org/jira/browse/HBASE-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106879#comment-13106879
]
Hudson commented on HBASE-4417:
-------------------------------
Integrated in HBase-TRUNK #2222 (See
[https://builds.apache.org/job/HBase-TRUNK/2222/])
HBASE-4417 HBaseAdmin.checkHBaseAvailable() doesn't close ZooKeeper
connections
(Stefan Seelmann)
tedyu :
Files :
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java
> 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
> Assignee: Stefan Seelmann
> Priority: Minor
> Fix For: 0.92.0, 0.90.5
>
> Attachments: HBASE-4417-0.90.diff, HBASE-4417-0.90.diff.v2,
> HBASE-4417-0.92.diff, HBASE-4417-0.92.diff.v2
>
>
> 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
