I triggered several time major_compaction between 22:30 and the time i
wrote the original email 00:58
From the log of one of the severs between those time no major compaction
was running a major_compaction ended at 22:23 on the same server but this
is because the number of file was high (after a
In 0.92, we can handle multiple compactions but we wait on major compact
if minor compactions are ongoing for the same store. It should be
enqueued and work after the minor compaction finishes, it's just not
immediately enqueued. See HBASE-5330 for some discussion on this. There
should be a log
Hi Nicolas,
Well
1. I don't see such message, on the second hand I'm not using debug
severity in the log (unless this is not a debug message)
2. If major compaction are just entering the compaction queue it seems to
me quite problematic; especially when you want to control the impact of
Can you show us some logs that exhibit this behavior?
Thx,
J-D
On Thu, Feb 23, 2012 at 2:58 PM, Mikael Sitruk mikael.sit...@gmail.com wrote:
Hi
Before filling a jira, I would like to check this with you.
It seems that the major compaction behavior changed between 0.90.x and 0.92
(not
