[
https://issues.apache.org/jira/browse/HBASE-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564846#comment-13564846
]
Hudson commented on HBASE-7673:
-------------------------------
Integrated in HBase-TRUNK #3817 (See
[https://builds.apache.org/job/HBase-TRUNK/3817/])
HBASE-7673 Incorrect error logging when a replication peer
is removed (Gabriel Reid via JD) (Revision 1439635)
Result = FAILURE
jdcryans :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationZookeeper.java
> 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
> Assignee: Gabriel Reid
> Priority: Minor
> Fix For: 0.96.0
>
> 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
