svn commit: r1233610 - /hbase/trunk/src/docbkx/performance.xml

[dm...@apache.org]

Author: dmeil
Date: Thu Jan 19 22:31:16 2012
New Revision: 1233610

URL: http://svn.apache.org/viewvc?rev=1233610&view=rev
Log:
performance.xml - added another paragraph in "One Hot Region" section.

Modified:
    hbase/trunk/src/docbkx/performance.xml

Modified: hbase/trunk/src/docbkx/performance.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/performance.xml?rev=1233610&r1=1233609&r2=1233610&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/performance.xml (original)
+++ hbase/trunk/src/docbkx/performance.xml Thu Jan 19 22:31:16 2012
@@ -358,7 +358,13 @@ Deferred log flush can be configured on 
     <title>Anti-Pattern:  One Hot Region</title>
     <para>If all your data is being written to one region at a time, then re-read the
     section on processing <link linkend="timeseries">timeseries</link> data.</para>
-    <para>Also, see <xref linkend="precreate.regions"/>, as well as <xref linkend="perf.configurations"/> </para>   
+    <para>Also, if you are pre-splitting regions and all your data is <emphasis>still</emphasis> winding up in a single region even though
+    your keys aren't monotonically increasing, confirm that your keyspace actually works with the split strategy.  There are a 
+    variety of reasons that regions may appear "well split" but won't work with your data.   As
+    the HBase client communicates directly with the RegionServers, this can be obtained via 
+    <link xlink:href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HTable.html#getRegionLocation%28byte[]%29">HTable.getRegionLocation</link>.
+    </para>
+    <para>See <xref linkend="precreate.regions"/>, as well as <xref linkend="perf.configurations"/> </para>   
   </section>
 
   </section>  <!--  writing -->