[
https://issues.apache.org/jira/browse/HBASE-12376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-12376:
--------------------------
Attachment:
0001-12376-HBaseAdmin-leaks-ZK-connections-if-failure-sta.version2.patch
Thanks for nice review [~busbey] This version addresses all your comments.
Regards....
bq. Wrap the ct.stop() call in a try/catch(RuntimeException) that logs a
warning.
So, you say RuntimeException in case an unexpected Exception (OOME or
something?). The stop does pretty good job at catching all other crap. This a
style you think we should institute throughout?
Thanks.
> HBaseAdmin leaks ZK connections if failure starting watchers
> (ConnectionLossException)
> --------------------------------------------------------------------------------------
>
> Key: HBASE-12376
> URL: https://issues.apache.org/jira/browse/HBASE-12376
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
> Affects Versions: 0.98.7, 0.94.24
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Attachments:
> 0001-12376-HBaseAdmin-leaks-ZK-connections-if-failure-sta.patch,
> 0001-12376-HBaseAdmin-leaks-ZK-connections-if-failure-sta.version2.patch
>
>
> This is a 0.98 issue that some users have been running into mostly running
> Canary and for whatever reason, setup of zk connection fails, usually with a
> ConnectionLossException. End result is ugly leak zk connections. ZKWatcher
> created instances are just left hang out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
