You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Misty Stanley-Jones (JIRA)" <ji...@apache.org> on 2014/08/07 01:12:13 UTC

[jira] [Updated] (HBASE-11629) Operational concerns for Replication should call out ZooKeeper

     [ https://issues.apache.org/jira/browse/HBASE-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Misty Stanley-Jones updated HBASE-11629:
----------------------------------------

    Attachment: HBASE-11629.patch

Here you go, and I tried git format-patch too.

> 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
>            Assignee: Misty Stanley-Jones
>         Attachments: HBASE-11629.patch
>
>
> 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
(v6.2#6252)