[
https://issues.apache.org/jira/browse/HBASE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525375#comment-16525375
]
stack commented on HBASE-6028:
------------------------------
[~mogoel] taking a look, on [[email protected]] 's comment, it would be nice
if you could correlate the interrupt of an ongoing compaction with the
exception you get out of the CompactionRunner but figuring that will be an
awkward untangling of the high-level thrown exception digging down to find the
ClosedByInterruptException or whatever other form the interrupt may bubble up
as. The code you add will be brittle too as you'll likely not figure all the
ways in which your interrupt stops the compaction. Change the ERROR to a WARN
instead? A failed compaction is not the end of the world. We'll retry so
perhaps a WARN is better?
On [~busbey] suggestion, let me help you figure how to update doc...
> Implement a cancel for in-progress compactions
> ----------------------------------------------
>
> Key: HBASE-6028
> URL: https://issues.apache.org/jira/browse/HBASE-6028
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: Derek Wollenstein
> Assignee: Mohit Goel
> Priority: Minor
> Labels: beginner
> Attachments: HBASE-6028.master.006.patch
>
>
> Depending on current server load, it can be extremely expensive to run
> periodic minor / major compactions. It would be helpful to have a feature
> where a user could use the shell or a client tool to explicitly cancel an
> in-progress compactions. This would allow a system to recover when too many
> regions became eligible for compactions at once
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
