Repository: hbase
Updated Branches:
  refs/heads/master 8c3697b0d -> 0209e1c76


HBASE-6994 minor doc update about DEFAULT_ACCEPTABLE_FACTOR (Liang Xie)


Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/0209e1c7
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/0209e1c7
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/0209e1c7

Branch: refs/heads/master
Commit: 0209e1c760fc53b84992cff5f6b37d7b49e4a749
Parents: 8c3697b
Author: Misty Stanley-Jones <[email protected]>
Authored: Tue Oct 7 13:17:05 2014 +1000
Committer: Misty Stanley-Jones <[email protected]>
Committed: Tue Oct 7 13:17:48 2014 +1000

----------------------------------------------------------------------
 src/main/docbkx/book.xml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/0209e1c7/src/main/docbkx/book.xml
----------------------------------------------------------------------
diff --git a/src/main/docbkx/book.xml b/src/main/docbkx/book.xml
index c337917..b2b4c78 100644
--- a/src/main/docbkx/book.xml
+++ b/src/main/docbkx/book.xml
@@ -2262,26 +2262,26 @@ rs.close();
             of time. </para>
           <para>The way to calculate how much memory is available in HBase for 
caching is: </para>
           <programlisting>
-            number of region servers * heap size * hfile.block.cache.size * 
0.85
+            number of region servers * heap size * hfile.block.cache.size * 
0.99
         </programlisting>
           <para>The default value for the block cache is 0.25 which represents 
25% of the available
-            heap. The last value (85%) is the default acceptable loading 
factor in the LRU cache
+            heap. The last value (99%) is the default acceptable loading 
factor in the LRU cache
             after which eviction is started. The reason it is included in this 
equation is that it
             would be unrealistic to say that it is possible to use 100% of the 
available memory
             since this would make the process blocking from the point where it 
loads new blocks.
             Here are some examples: </para>
           <itemizedlist>
             <listitem>
-              <para>One region server with the default heap size (1GB) and the 
default block cache
-                size will have 217MB of block cache available.</para>
+              <para>One region server with the default heap size (1 GB) and 
the default block cache
+                size will have 253 MB of block cache available.</para>
             </listitem>
             <listitem>
-              <para>20 region servers with the heap size set to 8GB and a 
default block cache size
-                will have 34GB of block cache.</para>
+              <para>20 region servers with the heap size set to 8 GB and a 
default block cache size
+                will have 39.6 of block cache.</para>
             </listitem>
             <listitem>
-              <para>100 region servers with the heap size set to 24GB and a 
block cache size of 0.5
-                will have about 1TB of block cache.</para>
+              <para>100 region servers with the heap size set to 24 GB and a 
block cache size of 0.5
+                will have about 1.16 TB of block cache.</para>
             </listitem>
         </itemizedlist>
         <para>Your data is not the only resident of the block cache. Here are 
others that you may have to take into account:

Reply via email to