HBASE-11629 Operational concerns for Replication should call out ZooKeeper (Misty Stanley Jones)

This commit is contained in:
stack 2014-08-07 08:24:32 -07:00
parent 12d9697d93
commit 3fdc6a2b72
2 changed files with 36 additions and 9 deletions

View File

@ -1569,13 +1569,32 @@ public class MyHBaseIntegrationTest {
<para>We don't have many but what we have we list below. All are subject to challenge of
course but until then, please hold to the rules of the road.
</para>
<section xml:id="design.invariants.zk.data">
<title>No permanent state in ZooKeeper</title>
<para>ZooKeeper state should transient (treat it like memory). If deleted, hbase
should be able to recover and essentially be in the same state<footnote><para>There are currently
a few exceptions that we need to fix around whether a table is enabled or disabled</para></footnote>.
</para>
</section>
<section xml:id="design.invariants.zk.data">
<title>No permanent state in ZooKeeper</title>
<para>ZooKeeper state should transient (treat it like memory). If ZooKeeper state is
deleted, hbase should be able to recover and essentially be in the same
state.</para>
<itemizedlist>
<title>Exceptions</title>
<listitem>
<para>There are currently a few exceptions that we need to fix around
whether a table is enabled or disabled.</para>
</listitem>
<listitem>
<para>Replication data is currently stored only in ZooKeeper. Deleting
ZooKeeper data related to replication may cause replication to be
disabled. Do not delete the replication tree,
<filename>/hbase/replication/</filename>.</para>
<warning>
<para>Replication may be disrupted and data loss may occur if you delete
the replication tree (<filename>/hbase/replication/</filename>) from
ZooKeeper. Follow progress on this issue at <link
xlink:href="https://issues.apache.org/jira/browse/HBASE-10295"
>HBASE-10295</link>.</para>
</warning>
</listitem>
</itemizedlist>
</section>
</section> <!-- design.invariants -->

View File

@ -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>
@ -1264,6 +1264,14 @@ false
<para>HBase replication maintains its state in ZooKeeper. By default, the state is
contained in the base node <filename>/hbase/replication</filename>. This node contains
two child nodes, the <code>Peers</code> znode and the <code>RS</code> znode.</para>
<warning>
<para>Replication may be disrupted and data loss may occur if you delete the
replication tree (<filename>/hbase/replication/</filename>) from ZooKeeper. This is
despite the information about invariants at <xref
linkend="design.invariants.zk.data"/>. Follow progress on this issue at <link
xlink:href="https://issues.apache.org/jira/browse/HBASE-10295"
>HBASE-10295</link>.</para>
</warning>
</listitem>
</varlistentry>
<varlistentry>