[
https://issues.apache.org/jira/browse/HBASE-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089285#comment-14089285
]
Sean Busbey commented on HBASE-11629:
-------------------------------------
+1 LGTM
{quote}
@@ -1141,10 +1141,10 @@ false
replicate and keeps track of the current position inside ZooKeeper to
simplify failure
recovery. That position, as well as the queue of WALs to process, may be
different for every
slave cluster.</para>
-
+
<para>The clusters participating in replication can be of different sizes.
The master
cluster relies on randomization to attempt to balance the stream of
replication on the slave clusters</para>
-
+
<para>HBase supports master/master and cyclic replication as well as
replication to multiple
slaves.</para>
{quote}
nit: unrelated whitespace change.
> 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)
