[
https://issues.apache.org/jira/browse/HBASE-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927696#action_12927696
]
Nicolas Spiegelberg commented on HBASE-3160:
--------------------------------------------
@Jeff: The bug wasn't related to the priority compaction code. The problem was
in CompactSplitThread.requestCompaction(). If the user requested a major
compaction, then the code would issue HRegion.setForceMajorCompaction(true).
however, if that region required a compaction while the HRegion was waiting in
the compact queue, then the code would call setForceMajorCompaction(false) and
downgrade the compaction request.
> Compactions: Use more intelligent priorities for PriorityCompactionQueue
> ------------------------------------------------------------------------
>
> Key: HBASE-3160
> URL: https://issues.apache.org/jira/browse/HBASE-3160
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.89.20100924, 0.90.0
> Reporter: Nicolas Spiegelberg
> Assignee: Nicolas Spiegelberg
> Fix For: 0.90.0
>
> Attachments: HBASE-3160.patch
>
>
> One of the problems with the current compaction queue is that we have a very
> low granularity on the importance of the various compactions in the queue.
> If a StoreFile count exceeds 15 files, only then do we bump via enum change.
> We should instead look into more intelligent, granular priority metrics for
> choosing the next compaction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
