[
https://issues.apache.org/jira/browse/HBASE-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488281#comment-13488281
]
Hadoop QA commented on HBASE-6904:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12551633/HBASE-6904-94.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3207//console
This message is automatically generated.
> In the HBase shell, an error is thrown that states replication-related znodes
> already exist
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-6904
> URL: https://issues.apache.org/jira/browse/HBASE-6904
> Project: HBase
> Issue Type: Bug
> Components: Replication, Zookeeper
> Affects Versions: 0.92.0, 0.92.1, 0.96.0
> Reporter: Aleksandr Shulman
> Assignee: Gregory Chanan
> Priority: Minor
> Fix For: 0.94.3, 0.96.0
>
> Attachments: HBASE-6904-94.patch, HBASE-6904.patch
>
>
> On a replication-enabled cluster, querying the list_peers produces the error
> lines shown below. It doesn't appear that anything is broken in terms of
> functionality.
> Stack trace:
> hbase(main):001:0> list_peers
> 12/09/29 14:41:03 ERROR zookeeper.RecoverableZooKeeper: Node
> /hbase/replication/peers already exists and this is not a retry
> 12/09/29 14:41:03 ERROR zookeeper.RecoverableZooKeeper: Node
> /hbase/replication/rs already exists and this is not a retry
> PEER ID CLUSTER KEY
> 0 row(s) in 0.4650 seconds
--
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
