Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> the occasion of the major compact?


Copy link to this message
-
Re: the occasion of the major compact?
Thanks for your response.

I knew that major compact can be triggered based on client, time and
size. In my situation, I have to close the functionality of major
compact. So, if I set the ‘hbase.hregion.majorcompaction’ into 0, it
will close all the three situations or I have to set it separately for
each case. BTW, my hbase version is 0.92.

Thanks!

Yong

On Thu, Jan 26, 2012 at 3:09 PM, Mikael Sitruk <[EMAIL PROTECTED]> wrote:
> look at the thread http://search-hadoop.com/m/GHUWQ1xnbj21, it explain a
> lot on major compaction and enhancement over versions
>
> Mikael.S
>
>
> On Thu, Jan 26, 2012 at 3:51 PM, Damien Hardy <[EMAIL PROTECTED]> wrote:
>
>> Le 26/01/2012 14:43, yonghu a écrit :
>> > Hello,
>> >
>> > I read this blog http://outerthought.org/blog/465-ot.html. It mentions
>> > that every 24 hours the major compaction will occur. My question is
>> > that if there are any other conditions which can trigger major
>> > compaction happening? For example, when the size of store file reaches
>> > the threshold (I think this will cause minor compaction or region file
>> > split, not major compaction, but not quite sure).
>> >
>> > Thanks!
>> >
>> > Yong
>>
>> Hello,
>> I think when there is massive delete on the table or change table
>> attribute like TTL (that is susseptible of remove a lot of
>> versions/rows) or COMPRESSION wich gain a lot of disk space on each region.
>>
>> Cheers,
>>
>> --
>> Damien
>>
>>
>
>
> --
> Mikael.S