You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2014/08/06 08:43:13 UTC
[jira] [Commented] (HBASE-11535) ReplicationPeer map is not thread
safe
[ https://issues.apache.org/jira/browse/HBASE-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087331#comment-14087331 ]
Jonathan Hsieh commented on HBASE-11535:
----------------------------------------
hi [~virag], i think you missed the usage in peerRemoved (need to use the atomic remove method there). Also though this applies to trunk and branch-1 it does not to 0.98. If you want the fix there it would be great if you could provide a 0.98 version of the patch as well.
> ReplicationPeer map is not thread safe
> --------------------------------------
>
> Key: HBASE-11535
> URL: https://issues.apache.org/jira/browse/HBASE-11535
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 0.98.4
> Reporter: Virag Kothari
> Assignee: Virag Kothari
> Attachments: HBASE-11535.patch
>
>
> ReplicationPeersZKImpl has a map of Peer id to ReplicationPeer which is accessed by replication source threads through getStatusOfPeer(). So, it needs to be thread safe.
--
This message was sent by Atlassian JIRA
(v6.2#6252)