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/24 20:00:32 UTC

svn commit: r1377013 - /hbase/trunk/src/docbkx/upgrading.xml

Author: stack
Date: Fri Aug 24 18:00:32 2012
New Revision: 1377013

URL: http://svn.apache.org/viewvc?rev=1377013&view=rev
Log:
Fix type -- from Shrijeet Paliwal

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

Modified: hbase/trunk/src/docbkx/upgrading.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/upgrading.xml?rev=1377013&r1=1377012&r2=1377013&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/upgrading.xml (original)
+++ hbase/trunk/src/docbkx/upgrading.xml Fri Aug 24 18:00:32 2012
@@ -194,7 +194,7 @@ See this blog post for additional inform
 </title>
 <para>0.92.0 stores data in a new format, <xref linkend="hfilev2" />.   As HBase runs, it will move all your data from HFile v1 to HFile v2 format.  This auto-migration will run in the background as flushes and compactions run.
 HFile V2 allows HBase run with larger regions/files.  In fact, we encourage that all HBasers going forward tend toward Facebook axiom #1, run with larger, fewer regions.
-If you have lots of regions now -- more than 100s per host -- you should look into setting your region size up after you move to 0.92.0 (In 0.92.0, default size is not 1G, up from 256M), and then running online merge tool (See âHBASE-1621 merge tool should work on online cluster, but disabled tableâ).
+If you have lots of regions now -- more than 100s per host -- you should look into setting your region size up after you move to 0.92.0 (In 0.92.0, default size is now 1G, up from 256M), and then running online merge tool (See âHBASE-1621 merge tool should work on online cluster, but disabled tableâ).
 </para>
 </section>
     </section>