Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 25 Jan 2013 13:23:12 +0000 (UTC)
From: "Gabriel Reid (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12629267.1359119966243.190825.1359120192912@arcas>
In-Reply-To: <JIRA.12629267.1359119966243@arcas>
References: <JIRA.12629267.1359119966243@arcas>
Subject: [jira] [Updated] (HBASE-7673) Incorrect error logging when a
 replication peer is removed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Reid updated HBASE-7673:
--------------------------------

    Status: Patch Available  (was: Open)
    
> Incorrect error logging when a replication peer is removed
> ----------------------------------------------------------
>
>                 Key: HBASE-7673
>                 URL: https://issues.apache.org/jira/browse/HBASE-7673
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 0.96.0
>            Reporter: Gabriel Reid
>            Priority: Minor
>         Attachments: HBASE-7673.patch
>
>
> When a replication peer is removed (and all goes well), the following error is still logged:
> {noformat}[ERROR][14:14:21,504][ventThread] org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager - The queue we wanted to close is missing peer-state{noformat}
> This is due to a watch being set on the peer-state node under the replication peer node in ZooKeeper, and the ReplicationSource#PeersWatcher doesn't correctly discern between nodes when it gets nodeDeleted messages.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira