HBASE-6076 Improve h.r.global.memstore.upper(lower)Limit description (Alex Baranau via JD)

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1342079 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jean-Daniel Cryans 2012-05-23 22:32:19 +00:00
parent 1f242db7f7
commit 1c0181bb61
1 changed files with 5 additions and 3 deletions

View File

@ -305,14 +305,16 @@
<name>hbase.regionserver.global.memstore.upperLimit</name> <name>hbase.regionserver.global.memstore.upperLimit</name>
<value>0.4</value> <value>0.4</value>
<description>Maximum size of all memstores in a region server before new <description>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.
Updates are blocked and flushes are forced until size of all memstores
in a region server hits hbase.regionserver.global.memstore.lowerLimit.
</description> </description>
</property> </property>
<property> <property>
<name>hbase.regionserver.global.memstore.lowerLimit</name> <name>hbase.regionserver.global.memstore.lowerLimit</name>
<value>0.35</value> <value>0.35</value>
<description>When memstores are being forced to flush to make room in <description>Maximum size of all memstores in a region server before
memory, keep flushing until we hit this mark. Defaults to 35% of heap. flushes are forced. Defaults to 35% of heap.
This value equal to hbase.regionserver.global.memstore.upperLimit causes This value equal to hbase.regionserver.global.memstore.upperLimit causes
the minimum possible flushing to occur when updates are blocked due to the minimum possible flushing to occur when updates are blocked due to
memstore limiting. memstore limiting.