[
https://issues.apache.org/jira/browse/HBASE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279277#comment-13279277
]
Derek Wollenstein commented on HBASE-6028:
------------------------------------------
@Stack --
I just looked at the current version -- it looks like the current check for
this is in StoreFile.Writer.compactStore(final Collection<StoreFile>
filesToCompact,
final boolean majorCompaction, final long maxId).
// check periodically to see if a system stop is requested
if (Store.closeCheckInterval > 0) {
bytesWritten += kv.getLength();
if (bytesWritten > Store.closeCheckInterval) {
bytesWritten = 0;
if (!this.region.areWritesEnabled()) {
writer.close();
fs.delete(writer.getPath(), false);
throw new InterruptedIOException(
"Aborting compaction of store " + this +
" in region " + this.region +
" because user requested stop.");
}
}
}
So we could go ahead and actually put an explicit "compactions enabled"
feature. This would also help if I wanted to later on add a feature to put in
a time window for compactions.
> 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
> Priority: Minor
> Labels: compaction, operations, regionserver
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
