You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by jx...@apache.org on 2012/10/26 22:28:23 UTC

svn commit: r1402650 - /hbase/trunk/src/docbkx/book.xml

Author: jxiang
Date: Fri Oct 26 20:28:23 2012
New Revision: 1402650

URL: http://svn.apache.org/viewvc?rev=1402650&view=rev
Log:
HBASE-6223 Document hbck improvements: HBASE-6173, HBASE-5360

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=1402650&r1=1402649&r2=1402650&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/book.xml (original)
+++ hbase/trunk/src/docbkx/book.xml Fri Oct 26 20:28:23 2012
@@ -2683,6 +2683,12 @@ listing of all the splits present in all
 <programlisting>
 $ ./bin/hbase hbck -details
 </programlisting>
+If you just want to know if some tables are corrupted, you can limit hbck to identify inconsistencies
+in only specific tables. For example the following command would only attempt to check table
+TableFoo and TableBar. The benefit is that hbck will run in less time.
+<programlisting>
+$ ./bin/hbase/ hbck TableFoo TableBar
+</programlisting>
 	</section>
 	<section><title>Inconsistencies</title>
 	<para>
@@ -2812,7 +2818,7 @@ integrity options.
 		</listitem>
 	</itemizedlist>
 Finally, there are safeguards to limit repairs to only specific tables. For example the following
-command would only attempt to repair table TableFoo and TableBar.
+command would only attempt to check and repair table TableFoo and TableBar.
 <programlisting>
 $ ./bin/hbase/ hbck -repair TableFoo TableBar
 </programlisting>
@@ -2845,6 +2851,19 @@ NOTE: This tool is not as clever as uber
 can complete.
 If the tool succeeds you should be able to start hbase and run online repairs if necessary.
 	</section>
+	<section><title>Special cases: Offline split parent</title>
+    <para>
+Once a region is split, the offline parent will be cleaned up automatically. Sometimes, daughter regions
+are split again before their parents are cleaned up. HBase can clean up parents in the right order. However,
+there could be some lingering offline split parents sometimes. They are in META, in HDFS, and not deployed.
+But HBase can't clean them up. In this case, you can use the <code>-fixSplitParents</code> option to reset
+them in META to be online and not split. Therefore, hbck can merge them with other regions if fixing
+overlapping regions option is used.
+    </para>
+    <para>
+This option should not normally be used, and it is not in <code>-fixAll</code>.
+    </para>
+	</section>
 	</section>
   </appendix>