hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kashif Jawed Siddiqui <kashi...@huawei.com>
Subject RE: why major_compaction does more performance consumption than minor_compaction ?
Date Fri, 20 Jun 2014 09:17:27 GMT
Check this article: http://www.ngdata.com/visualizing-hbase-flushes-and-compactions/


This e-mail and attachments contain confidential information from HUAWEI, which is intended
only for the person or entity whose address is listed above. Any use of the information contained
herein in any way (including, but not limited to, total or partial disclosure, reproduction,
or dissemination) by persons other than the intended recipient's) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately and delete it!

-----Original Message-----
From: Fx_Bull [mailto:jhaobull@gmail.com] 
Sent: 20 June 2014 14:41
To: user
Subject: why major_compaction does more performance consumption than minor_compaction ?

hello everyone!

Differenct between them:

1、minor_compact will select best storeFiles to compact。
2、major_compact will select all storeFiles to compact and do some clean work。

RegionServer holds only one compactSplitThread ,and only one compact task run !

3、The compaction task just scans all the storefiles and then merge one, so I hold the opinon
that major compact only cost more time than minor .

best regards!!
View raw message