[
https://issues.apache.org/jira/browse/HBASE-20597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488217#comment-16488217
]
Andrew Purtell commented on HBASE-20597:
----------------------------------------
To https://git-wip-us.apache.org/repos/asf/hbase.git
498f3bf953..1b70763b9e branch-1 -> branch-1
66941d70bb..8040c0ca76 branch-1.2 -> branch-1.2
94001b35a7..b50e149804 branch-1.3 -> branch-1.3
cd6397be6b..7182df3bd3 branch-1.4 -> branch-1.4
12d75724d7..60dcef289b branch-2 -> branch-2
86a9b80ff4..6ecb444208 branch-2.0 -> branch-2.0
3a805074a2..9fbce1668b master -> master
> Use a lock to serialize access to a shared reference to ZooKeeperWatcher in
> HBaseReplicationEndpoint
> ----------------------------------------------------------------------------------------------------
>
> Key: HBASE-20597
> URL: https://issues.apache.org/jira/browse/HBASE-20597
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.4.4
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.3.3, 2.0.1, 1.4.5
>
> Attachments: HBASE-20597-branch-1.patch, HBASE-20597.patch
>
>
> The code that closes down a ZKW that fails to initialize when attempting to
> connect to the remote cluster is not MT safe and can in theory leak
> ZooKeeperWatcher instances. The allocation of a new ZKW and store to the
> reference is not atomic. Might have concurrent allocations with only one
> winning store, leading to leaked ZKW instances.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
