Any one knows what compaction queue size is meant?
By doc's definition:
*9.2.5.* hbase.regionserver.compactionQueueSize Size of the compaction
queue. This is the number of stores in the region that have been targeted
for compaction.
- Is it the *number of Store* of regionserver need to be major compacted
? or numbers of which is* being* compacted currently ?
I have a job writing data in a hotspot style using sequential key(non
distributed) with 1 family so that 1 Store each region.
I was discovering that at some time it got *regionserver
compaction-queue-size = 4*.(I check it from Ambari). That's theoretically
impossible since I have only *one Store *to write(sequential key) at any
time, incurring only one major compaction is more reasonable.
- Then I dig into the logs ,found there is no thing about hints of
queue size > 0: Every major compaction just say *"This selection was in
queue for 0sec", *I don't really understand what's it to means? is it
saying hbase has nothing in compaction queue?
013-11-26 12:28:00,778 INFO
[regionserver60020-smallCompactions-1385440028938] regionserver.HStore:
Completed major compaction of 3 file(s) in f1 of myTable.key.md5.... into
md5....(size=607.8 M), total size for store is 645.8 M.*This selection was
in queue for 0sec*, and took 39sec to execute.
- Just more confusing is : Isn't multi-thread enabled at earlier version
that will allocate each compaction job to a thread , by this reason why
there exists compaction queue waiting for processing ?
