[
https://issues.apache.org/jira/browse/HBASE-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776905#comment-13776905
]
Sergey Shelukhin commented on HBASE-9648:
-----------------------------------------
I think in the reported case there was more than one file in store (and thus
the candidate list), it's that it was selecting one expired file.
Judging by HBASE-6059 description and comments, we actually don't have to
generate a new file unless we are talking about the highest-seqid file in the
region (which also implies not removing the last file).
So it may make sense to allow lazy-writer code to run if there're files
remaining in store (which would presumably mean for ever minor compactions). In
that case not running expired check on single last file would be enough.
> collection one expired storefile causes it to be replaced by another expired
> storefile
> --------------------------------------------------------------------------------------
>
> Key: HBASE-9648
> URL: https://issues.apache.org/jira/browse/HBASE-9648
> Project: HBase
> Issue Type: Bug
> Components: Compaction
> Reporter: Sergey Shelukhin
> Assignee: Jean-Marc Spaggiari
> Attachments: HBASE-9648-v0-0.94.patch, HBASE-9648-v0-trunk.patch
>
>
> There's a shortcut in compaction selection that causes the selection of
> expired store files to quickly delete.
> However, there's also the code that ensures we write at least one file to
> preserve seqnum. This new empty file is "expired", because it has no data,
> presumably.
> So it's collected again, etc.
> This affects 94, probably also 96.
--
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
