I recommend reading the Bigtable paper to learn more about these
architectural things.
On 4/7/10 8:32 AM, "ChingShen" wrote:
> 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
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
: Re: Why does the default hbase.hstore.compactionThreshold is
> 3?
>
> It does incremental compacting since you don't want to spend too much
> time doing the compactions, and you don't want to compact very large
> store files with much smaller ones (that would result i
It does incremental compacting since you don't want to spend too much
time doing the compactions, and you don't want to compact very large
store files with much smaller ones (that would result in rewriting the
same data x times per day). Looking at Store.compact, you can see this
comment:
Hi,
I got when the menstore reaches a configurable size(64MB), it's flushed to
HDFS, and create a new StoreFile, therefore, when these StoreFiles more
than 3 files, they will be compacted to a single StoreFile. But, if the
default hbase.hstore.compactionThreshold is 3, does it mean that a compa
