hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11629) Operational concerns for Replication should call out ZooKeeper
Date Thu, 31 Jul 2014 20:00:38 GMT

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

Andrew Purtell commented on HBASE-11629:

bq. Hopefully one day we can get back to a state where the zk design invariant holds again
(other state only kept in zk is whether table is disabled or not).

Do we currently have a JIRA open for this? I've lost track.

> Operational concerns for Replication should call out ZooKeeper
> --------------------------------------------------------------
>                 Key: HBASE-11629
>                 URL: https://issues.apache.org/jira/browse/HBASE-11629
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation, Replication
>            Reporter: Sean Busbey
> Our [design invariants state that ZooKeeper data is safe to delete|http://hbase.apache.org/book/developing.html#design.invariants.zk.data].
However, [replication only stores its data in zookeeper|http://hbase.apache.org/replication.html#Replication_Zookeeper_State].

> This can lead to operators accidentally disabling their replication set up while attempting
to recover from an unrelated issue by clearing the zk state.
> We should update the [operational concerns section on replication|http://hbase.apache.org/book/cluster_replication.html]
to call out that the /hbase/replication tree should not be deleted. We should probably also
add a warning to the set up steps.

This message was sent by Atlassian JIRA

View raw message