hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ChingShen <chingshenc...@gmail.com>
Subject Re: Why does the default hbase.hstore.compactionThreshold is 3?
Date Wed, 07 Apr 2010 15:32:59 GMT
Thanks, JG

   As you mentioned at HBASE-2375, if we make decision to split based on
aggregate size of all StoreFiles, and compactionThreshold is 5, does it mean
that we don't need to do compaction forever?
and please allow me to ask a silly question about compaction, why do we need
the minor/major compaction in HBase? what's advantages of the minor/major
compaction? speed up for read operations?

Thanks in advance.


On Wed, Apr 7, 2010 at 2:06 PM, Jonathan Gray <jgray@facebook.com> wrote:

> Shen,
> You are right.  Currently the default flush size is 64MB, the
> compactionThreshold is 3, and the splitSize/max.filesize is 256MB.  So we
> end up compacting into a 192MB file when filling an empty region.
> Take a look at HBASE-2375 (
> https://issues.apache.org/jira/browse/HBASE-2375).  That issue deals with
> changing some of this behavior as well as the defaults.
> JG

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message