From f3b3d86d21b1a76e0f51082cd9b1e4dc40fc2427 Mon Sep 17 00:00:00 2001 From: Yechao Chen Date: Fri, 9 Nov 2018 16:32:11 +0800 Subject: [PATCH] HBASE-21460 correct Document Configurable Bucket Sizes in bucketCache --- src/main/asciidoc/_chapters/architecture.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/asciidoc/_chapters/architecture.adoc b/src/main/asciidoc/_chapters/architecture.adoc index e1905bc884..9bc322b353 100644 --- a/src/main/asciidoc/_chapters/architecture.adoc +++ b/src/main/asciidoc/_chapters/architecture.adoc @@ -950,14 +950,14 @@ In the above, we set the BucketCache to be 4G. We configured the on-heap LruBlockCache have 20% (0.2) of the RegionServer's heap size (0.2 * 5G = 1G). In other words, you configure the L1 LruBlockCache as you would normally (as if there were no L2 cache present). link:https://issues.apache.org/jira/browse/HBASE-10641[HBASE-10641] 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 `hfile.block.cache.sizes` (instead of `hfile.block.cache.size`) to a comma-separated list of block sizes, ordered from smallest to largest, with no spaces. +To configurable multiple bucket sizes, configure the new property `hbase.bucketcache.bucket.sizes` (instead of `hbase.bucketcache.bucket.size`) 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. [source,xml] ---- - hfile.block.cache.sizes + hbase.bucketcache.bucket.sizes 4096,8192 ---- -- 1.8.3.1