Mozilla recently had to turn off automatic scheduled major compactions
because if they happen during our peak load time, they cause an IO delay
that can destabilize our client applications.
We need to put a replacement system in place as soon as possible that
can initiate the major compaction and ensure that it successfully
completed (See HBASE-2770).
It would be nice if the system could actually determine the health (i.e.
does it need to happen right now?) and dynamically schedule it based on
load, but that isn't a requirement for what we need to put in place
initially.
I would very much like to speak with anyone in the community that might
be willing to pick this up as a quick project to contrib to HBase and
get paid for it.
Stack has stated he is willing to mentor on the project, and we can also
pull in other expertise if needed. This could be just the medal to pin
on your chest if you are working toward getting HBase commit access.
(Did I mention getting paid for it?)
Thanks for your time,
Daniel Einspanjer
Metrics Architect
Mozilla Corporation
