[
https://issues.apache.org/jira/browse/HBASE-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626107#comment-13626107
]
Sergey Shelukhin commented on HBASE-8299:
-----------------------------------------
{code}potentialMatchFiles.size() > bestSelection.size(){code} is always true
initially and true for any larger potential match after that.
If no compaction is in ratio (which can be true in normal case), it would
always do the maximum possible compaction, wouldn't it?
50 1 1, minfiles 3 would major compact as far as I see, which seems wrong, it
should wait for more small files to appear.
> ExploringCompactionPolicy can get stuck in rare cases.
> ------------------------------------------------------
>
> Key: HBASE-8299
> URL: https://issues.apache.org/jira/browse/HBASE-8299
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.1
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-8299-0.patch
>
>
> If the files are very oddly sized then it's possible that
> ExploringCompactionPolicy can get stuck.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
