Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

hbase-5390. book.xml - adding section in Arch/Master about what happens if master dies. 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1243550 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Doug Meil 2012-02-13 15:00:51 +00:00
parent 0553fbc25b
commit 8e35106b38
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/docbkx/book.xml
View File

@ -1378,6 +1378,9 @@ if (!b) {
the client will requery the catalog tables to determine the new
location of the user region.
</para>
<para>See <xref linkend="master.runtime"/> for more information about the impact of the Master on HBase Client
communication.
</para>
<para>Administrative functions are handled through <link xlink:href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HBaseAdmin.html">HBaseAdmin</link>
</para>
<section xml:id="client.connections"><title>Connections</title>
@ -1661,6 +1664,15 @@ rs.close();
take over the Master role.
</para>
</section>
<section xml:id="master.runtime"><title>Runtime Impact</title>
<para>A common dist-list question is what happens to an HBase cluster when the Master goes down. Because the
HBase client talks directly to the RegionServers, the cluster can still function in a "steady
state." Additionally, per <xref linkend="arch.catalog"/> ROOT and META exist as HBase tables (i.e., are
not resident in the Master). However, the Master controls critical functions such as RegionServer failover and
completing region splits. So while the cluster can still run <emphasis>for a time</emphasis> without the Master,
the Master should be restarted as soon as possible.
</para>
</section>
<section xml:id="master.api"><title>Interface</title>
<para>The methods exposed by <code>HMasterInterface</code> are primarily metadata-oriented methods:
<itemizedlist>