Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-14326 Clarify that ExploringCompactionPolicy evaluates a selection of StoreFiles, not a single StoreFile

This commit is contained in:
Misty Stanley-Jones 2015-10-12 14:23:46 +10:00
parent ab677a19fc
commit 6a90e7b43b
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
hbase-common/src/main/resources/hbase-default.xml
View File

@ -736,7 +736,8 @@ possible configurations would overwhelm and obscure the important.
<property>
<name>hbase.hstore.compaction.min.size</name>
<value>134217728</value>
<description>A StoreFile smaller than this size will always be eligible for minor compaction.
<description>A StoreFile (or a selection of StoreFiles, when using ExploringCompactionPolicy)
smaller than this size will always be eligible for minor compaction.
HFiles this size or larger are evaluated by hbase.hstore.compaction.ratio to determine if
they are eligible. Because this limit represents the "automatic include"limit for all
StoreFiles smaller than this value, this value may need to be reduced in write-heavy
@ -750,7 +751,8 @@ possible configurations would overwhelm and obscure the important.
<property>
<name>hbase.hstore.compaction.max.size</name>
<value>9223372036854775807</value>
<description>A StoreFile larger than this size will be excluded from compaction. The effect of
<description>A StoreFile (or a selection of StoreFiles, when using ExploringCompactionPolicy)
larger than this size will be excluded from compaction. The effect of
raising hbase.hstore.compaction.max.size is fewer, larger StoreFiles that do not get
compacted often. If you feel that compaction is happening too often without much benefit, you
can try raising this value. Default: the value of LONG.MAX_VALUE, expressed in bytes.</description>