Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3E81911ABC for ; Wed, 6 Aug 2014 17:38:12 +0000 (UTC) Received: (qmail 99348 invoked by uid 500); 6 Aug 2014 17:38:12 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 99297 invoked by uid 500); 6 Aug 2014 17:38:12 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 99273 invoked by uid 99); 6 Aug 2014 17:38:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Aug 2014 17:38:12 +0000 Date: Wed, 6 Aug 2014 17:38:11 +0000 (UTC) From: "Virag Kothari (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11535) ReplicationPeer map is not thread safe MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087926#comment-14087926 ] Virag Kothari commented on HBASE-11535: --------------------------------------- Thanks for pointing that [~jmhsieh]. Updated based on your comments and also provided a 0.98 patch > 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 > Fix For: 0.98.6 > > Attachments: HBASE-11535.patch, HBASE-11535.patch, HBASE-11535_98.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)