hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Shulman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6904) In the HBase shell, an error is thrown that states replication-related znodes already exist
Date Wed, 31 Oct 2012 21:23:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488242#comment-13488242
] 

Aleksandr Shulman commented on HBASE-6904:
------------------------------------------

Is it actually a problem that the replication znodes exist? From the comments, it would seem
not. However, the author of this piece of code seemed to think it was a problem. How are we
reconciling those two things?
                
> 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.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

Mime
View raw message