From b09652bb82012225b644fc571ae928ea2e905d13 Mon Sep 17 00:00:00 2001 From: Esteban Gutierrez Date: Thu, 4 Jun 2015 16:21:53 -0700 Subject: [PATCH] HBASE-13729 Old hbase.regionserver.global.memstore.upperLimit and lowerLimit properties are ignored if present --- hbase-common/src/main/resources/hbase-default.xml | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/hbase-common/src/main/resources/hbase-default.xml b/hbase-common/src/main/resources/hbase-default.xml index ad07c57..25d29bb 100644 --- a/hbase-common/src/main/resources/hbase-default.xml +++ b/hbase-common/src/main/resources/hbase-default.xml @@ -296,19 +296,23 @@ possible configurations would overwhelm and obscure the important. hbase.regionserver.global.memstore.size - 0.4 + Maximum size of all memstores in a region server before new - updates are blocked and flushes are forced. Defaults to 40% of heap. + updates are blocked and flushes are forced. Defaults to 40% of heap (0.4). Updates are blocked and flushes are forced until size of all memstores - in a region server hits hbase.regionserver.global.memstore.size.lower.limit. + in a region server hits hbase.regionserver.global.memstore.size.lower.limit. + The default value in this configuration has been intentionally left emtpy in order to + honor the old hbase.regionserver.global.memstore.upperLimit property if present. hbase.regionserver.global.memstore.size.lower.limit - 0.95 + Maximum size of all memstores in a region server before flushes are forced. - Defaults to 95% of hbase.regionserver.global.memstore.size. + Defaults to 95% of hbase.regionserver.global.memstore.size (0.95). A 100% value for this value causes the minimum possible flushing to occur when updates are - blocked due to memstore limiting. + blocked due to memstore limiting. + The default value in this configuration has been intentionally left emtpy in order to + honor the old hbase.regionserver.global.memstore.lowerLimit property if present. hbase.regionserver.optionalcacheflushinterval -- 2.4.2