From d56dfd2a8bb6c885d7cc1abc2df84ac1d2737e7b Mon Sep 17 00:00:00 2001
From: Michael Stack <stack@duboce.net>
Date: Mon, 2 Jun 2014 08:59:03 -0700
Subject: [PATCH] Add pointer to blog on distributed log splitting

---
 src/main/docbkx/upgrading.xml | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/main/docbkx/upgrading.xml b/src/main/docbkx/upgrading.xml
index 33b68d87d6e..aa2bec15dec 100644
--- a/src/main/docbkx/upgrading.xml
+++ b/src/main/docbkx/upgrading.xml
@@ -291,7 +291,7 @@ Successfully completed Log splitting
                             regions.</para>
                     </listitem>
                     <listitem>
-                        <para> Distributed splitting is on by defaul. It should make region server
+                        <para> Distributed Log Splitting is on by default. It should make region server
                             failover faster. </para>
                     </listitem>
                     <listitem>
@@ -335,11 +335,13 @@ Successfully completed Log splitting
             </para>
         </section>
 
-        <section>
-            <title>Distributed splitting is on by default </title>
+        <section xml:id="dls">
+            <title>Distributed Log Splitting is on by default </title>
             <para>Previous, WAL logs on crash were split by the Master alone. In 0.92.0, log
                 splitting is done by the cluster (See See “HBASE-1364 [performance] Distributed
-                splitting of regionserver commit logs”). This should cut down significantly on the
+                splitting of regionserver commit logs” or see the blog post
+                <link xlink:href="http://blog.cloudera.com/blog/2012/07/hbase-log-splitting/">Apache HBase Log Splitting</link>).
+                This should cut down significantly on the
                 amount of time it takes splitting logs and getting regions back online again.
             </para>
         </section>