HBASE-11735 Document Configurable Bucket Sizes in bucketCache (Misty Stanley-Jones)
This commit is contained in:
parent
8a52d58a7b
commit
50f17935fd
|
@ -825,6 +825,33 @@ possible configurations would overwhelm and obscure the important.
|
|||
<description>When the size of a leaf-level, intermediate-level, or root-level
|
||||
index block in a multi-level block index grows to this size, the
|
||||
block is written out and a new block is started.</description>
|
||||
</property>
|
||||
<property>
|
||||
<name>hbase.bucketcache.ioengine</name>
|
||||
<value></value>
|
||||
<description>Where to store the contents of the bucketcache. One of: onheap,
|
||||
offheap, or file. If a file, set it to file:PATH_TO_FILE. See https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html for more information.
|
||||
</description>
|
||||
</property>
|
||||
<property>
|
||||
<name>hbase.bucketcache.combinedcache.enabled</name>
|
||||
<value>true</value>
|
||||
<description>Whether or not the bucketcache is used in league with the LRU
|
||||
on-heap block cache. In this mode, indices and blooms are kept in the LRU
|
||||
blockcache and the data blocks are kept in the bucketcache.</description>
|
||||
</property>
|
||||
<property>
|
||||
<name>hbase.bucketcache.size</name>
|
||||
<value>65536</value>
|
||||
<description>The size of the buckets for the bucketcache if you only use a single size.
|
||||
Defaults to the default blocksize, which is 64 * 1024.</description>
|
||||
</property>
|
||||
<property>
|
||||
<name>hbase.bucketcache.sizes</name>
|
||||
<value></value>
|
||||
<description>A comma-separated list of sizes for buckets for the bucketcache
|
||||
if you use multiple sizes. Should be a list of block sizes in order from smallest
|
||||
to largest. The sizes you use will depend on your data access patterns.</description>
|
||||
</property>
|
||||
<property>
|
||||
<name>hfile.format.version</name>
|
||||
|
|
|
@ -2384,6 +2384,20 @@ rs.close();
|
|||
In other words, you configure the L1 LruBlockCache as you would normally,
|
||||
as you would when there is no L2 BucketCache present.
|
||||
</para>
|
||||
<para><link xlink:href="https://issues.apache.org/jira/browse/HBASE-10641"
|
||||
>HBASE-10641</link> introduced the ability to configure multiple sizes for the
|
||||
buckets of the bucketcache, in HBase 0.98 and newer. To configurable multiple bucket
|
||||
sizes, configure the new property <option>hfile.block.cache.sizes</option> (instead of
|
||||
<option>hfile.block.cache.size</option>) to a comma-separated list of block sizes,
|
||||
ordered from smallest to largest, with no spaces. The goal is to optimize the bucket
|
||||
sizes based on your data access patterns. The following example configures buckets of
|
||||
size 4096 and 8192.</para>
|
||||
<screen language="xml"><![CDATA[
|
||||
<property>
|
||||
<name>hfile.block.cache.sizes</name>
|
||||
<value>4096,8192</value>
|
||||
</property>
|
||||
]]></screen>
|
||||
<note xml:id="direct.memory">
|
||||
<title>Direct Memory Usage In HBase</title>
|
||||
<para>The default maximum direct memory varies by JVM. Traditionally it is 64M
|
||||
|
|
Loading…
Reference in New Issue