You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by st...@apache.org on 2012/08/13 10:01:36 UTC
svn commit: r1372303 - /hbase/trunk/src/docbkx/book.xml
Author: stack
Date: Mon Aug 13 08:01:35 2012
New Revision: 1372303
URL: http://svn.apache.org/viewvc?rev=1372303&view=rev
Log:
Add link to Mohamed's blog entry
Modified:
hbase/trunk/src/docbkx/book.xml
Modified: hbase/trunk/src/docbkx/book.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/book.xml?rev=1372303&r1=1372302&r2=1372303&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/book.xml (original)
+++ hbase/trunk/src/docbkx/book.xml Mon Aug 13 08:01:35 2012
@@ -1681,7 +1681,11 @@ rs.close();
<section xml:id="master"><title>Master</title>
<para><code>HMaster</code> is the implementation of the Master Server. The Master server
is responsible for monitoring all RegionServer instances in the cluster, and is
- the interface for all metadata changes. In a distributed cluster, the Master typically runs on the <xref linkend="arch.hdfs.nn" />.
+ the interface for all metadata changes. In a distributed cluster, the Master typically runs on the <xref linkend="arch.hdfs.nn" /><footnote>
+ <para>J Mohamed Zahoor goes into some more detail on the Master Architecture in this blog posting, <link
+ xlink:href="http://blog.zahoor.in/2012/08/hbase-hmaster-architecture/">HBase HMaster Architecture
+ </link>.</para>
+ </footnote>
</para>
<section xml:id="master.startup"><title>Startup Behavior</title>
<para>If run in a multi-Master environment, all Masters compete to run the cluster. If the active