[
https://issues.apache.org/jira/browse/HBASE-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488291#comment-13488291
]
Aleksandr Shulman commented on HBASE-6904:
------------------------------------------
Well, I guess I'm as much concerned with whether the message is displayed at
the shell level (it's not great, we should fix it regardless). I'm more
concerned as to why we hit this failure mode to begin with. We should go down
to where the code throws the exception and investigate. If it's a spurious
exception, we need to get rid of it. If it's a meaningful exception, we need to
see why it occurs every time the shell starts (and stop it from happening).
> 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
