[
https://issues.apache.org/jira/browse/HBASE-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626870#comment-16626870
]
Allan Yang edited comment on HBASE-21224 at 9/25/18 6:51 AM:
-------------------------------------------------------------
An option is that when putting a store to the compaction queue, check the
queue, if the queue(only check the short compaction queue. since one store may
have generated several small HFiles to do a small compaction while waiting a
long compaction ) already has this store, then check the priority, if the
priority raised (meaning the store has more files now), delete the old item and
then queue the new one with greater priority. If the priority is the same, do
not queue this store again. Otherwise, do not queue it.
was (Author: allan163):
A option is that when putting a store to the compaction queue, check the queue,
if the queue(only check the short compaction queue. since one store may have
generated several small HFiles to do a small compaction while waiting a long
compaction ) already has this store, then check the priority, if the priority
raised (meaning the store has more files now), delete the old item and then
queue the new one with greater priority. If the priority is the same, do not
queue this store again. Otherwise, do not queue it.
> Handle compaction queue duplication
> -----------------------------------
>
> Key: HBASE-21224
> URL: https://issues.apache.org/jira/browse/HBASE-21224
> Project: HBase
> Issue Type: Improvement
> Components: Compaction
> Reporter: Xu Cang
> Priority: Minor
>
> Mentioned by [~allan163] that we may want to handle compaction queue
> duplication in this Jira https://issues.apache.org/jira/browse/HBASE-18451
> Creating this item for further assessment and discussion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
