[
https://issues.apache.org/jira/browse/HBASE-14485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907171#comment-14907171
]
Matteo Bertozzi commented on HBASE-14485:
-----------------------------------------
yeah, more general if something fail in the constructor all the connection open
and objects that should be closed are left open.
the exception example above was from parsing the cluster id that was causing a
zk leak
> ConnectionImplementation leaks on construction failure
> ------------------------------------------------------
>
> Key: HBASE-14485
> URL: https://issues.apache.org/jira/browse/HBASE-14485
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 2.0.0, 1.2.0, 1.0.1.1, 1.1.2, 1.3.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Attachments: HBASE-14485-v0.patch
>
>
> If an exception is thrown in the constructor of ConnectionImplementation we
> will have a leak zkRegistry, rpcClient, ...
> an example was clusterId parse error, causing zk (registry) leaks
> {noformat}
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
> ... 22 more
> Caused by: java.lang.ExceptionInInitializerError
> at org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
> at
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
> at
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:86)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:850)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
