Yes I did. Thanks for clarifying.
On Aug 10, 2014 3:04 PM, "Ted Yu" wrote:
bq. If I want aggressiveness from my cluster during these events I can
place a larger value here
You meant larger value for hbase.hstore.compaction.ratio, eight ?
Sounds good.
Cheers
On Sun, Aug 10, 2014 at 11:48 AM,
bq. If I want aggressiveness from my cluster during these events I can
place a larger value here
You meant larger value for hbase.hstore.compaction.ratio, eight ?
Sounds good.
Cheers
On Sun, Aug 10, 2014 at 11:48 AM, Geovanie Marquez <
geovanie.marq...@gmail.com> wrote:
> The default: 1.2F
> h
The default: 1.2F
hbase.hstore.compaction.ratio
For minor compaction, this ratio is used to determine whether a given
StoreFile which is larger than hbase.hstore.compaction.min.size is eligible
for compaction. Its effect is to limit compaction of large StoreFiles. The
value of hbase.hstore.compact
What is the value for the config parameter 'hbase.hstore.compaction.ratio' ?
Thanks
On Sun, Aug 10, 2014 at 7:17 AM, Geovanie Marquez <
geovanie.marq...@gmail.com> wrote:
> I notice that when I have a regions with store file counts greater
> than hbase.hstore.blockingStoreFiles,
> on cluster st
I notice that when I have a regions with store file counts greater
than hbase.hstore.blockingStoreFiles,
on cluster startup the number drops dramatically under this value to just
under the blockingStoreFile parameter value in a relative short amount of
time and then it stalls and doesn't fall more
