[
https://issues.apache.org/jira/browse/HBASE-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089390#comment-14089390
]
Hudson commented on HBASE-11629:
--------------------------------
ABORTED: Integrated in HBase-TRUNK #5379 (See
[https://builds.apache.org/job/HBase-TRUNK/5379/])
HBASE-11629 Operational concerns for Replication should call out ZooKeeper
(Misty Stanley Jones) (stack: rev 3fdc6a2b728c7280132bd31831f3838c24b0d0e3)
* src/main/docbkx/developer.xml
* src/main/docbkx/ops_mgt.xml
> 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
> Fix For: 2.0.0
>
> 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)
