hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From st...@apache.org
Subject svn commit: r1151747 - /hbase/trunk/src/docbkx/book.xml
Date Thu, 28 Jul 2011 06:34:57 GMT
Author: stack
Date: Thu Jul 28 06:34:56 2011
New Revision: 1151747

URL: http://svn.apache.org/viewvc?rev=1151747&view=rev
Log:
HBASE-4091 book.xml - description of block cache in arch, description of inMemory in schema
creation

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=1151747&r1=1151746&r2=1151747&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/book.xml (original)
+++ hbase/trunk/src/docbkx/book.xml Thu Jul 28 06:34:56 2011
@@ -261,6 +261,17 @@ admin.enableTable(table);               
   that includes versioning.  Take that into consideration when making your design, as well
as block size for the ColumnFamily.  
   </para>
   </section>
+  <section xml:id="cf.in.memory">
+  <title>
+  In-Memory ColumnFamilies
+  </title>
+  <para>ColumnFamilies can optionally be defined as in-memory.  Data is still persisted
to disk, just like any other ColumnFamily.  
+  In-memory blocks have the highest priority in the <xref linkend="block.cache" />,
but it is not a guarantee that the entire table
+  will be in memory.
+  </para>
+  <para>See <link xlink:href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/HColumnDescriptor.html">HColumnDescriptor</link>
for more information.
+  </para>
+  </section>
 
   </chapter>
 
@@ -984,9 +995,19 @@ HTable table2 = new HTable(conf2, "myTab
         </para>
       </section>
 
-
-      </section>
-
+     </section>  <!--  store -->
+     
+  <section xml:id="block.cache">
+     <title>Block Cache</title>
+      <para>The Block Cache contains three levels of block priority to allow for scan-resistance
and in-memory ColumnFamilies.  A block is added with an in-memory
+      flag if the containing ColumnFamily is defined in-memory, otherwise a block becomes
a single access priority.  Once a block is accessed again, it changes to multiple access.

+      This is used to prevent scans from thrashing the cache, adding a least-frequently-used
element to the eviction algorithm.  Blocks from in-memory ColumnFamilies
+      are the last to be evicted.
+      </para>
+      <para>
+       For more information, see the <link xlink:href="http://hbase.apache.org/xref/org/apache/hadoop/hbase/io/hfile/LruBlockCache.html">LruBlockCache
source</link>
+       </para>
+  </section>
 
   </section>
       <section xml:id="wal">



Mime
View raw message