[
https://issues.apache.org/jira/browse/HBASE-26987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743788#comment-17743788
]
Zheng Wang commented on HBASE-26987:
------------------------------------
Yeah, that's what the problem is.
One thing to consider about the solution is that if the number of files to be
compacted is too large and there is only one task in the queue, it will not
reflect the actual situation. [~zhangduo]
> The length of compact queue grows too big when the compacting is slow
> ---------------------------------------------------------------------
>
> Key: HBASE-26987
> URL: https://issues.apache.org/jira/browse/HBASE-26987
> Project: HBase
> Issue Type: Improvement
> Reporter: Zheng Wang
> Assignee: Zheng Wang
> Priority: Major
> Attachments: image-2022-04-29-10-26-09-351.png,
> image-2022-04-29-10-26-18-323.png, image-2022-04-29-10-26-24-087.png
>
>
> For some system compaction, we set the selectNow to false, so the file
> selecting will not be done until the compaction running, it brings side
> effect, if another compacting is slow, we may put lots of compaction to
> queue, because the filesCompacting of Hstore is empty in the meantime.
> An example shows at attachments, there are 154 regions and about 2000 hfiles,
> but the length of compact queue grows to 1391, it cause confusion and may
> trigger unexpected alarm.
> My approach is limit the compaction queue count, by compute the
> filesNotCompating and hbase.hstore.compaction.max.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
