[
https://issues.apache.org/jira/browse/HBASE-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845948#comment-13845948
]
Sergey Shelukhin commented on HBASE-9648:
-----------------------------------------
Makes sense... I can move the other patch for different jira. Technically, in
compaction policy, last candidate is not necessarily the latest file in store
as some files might not be candidates (for example, already compacting if there
are multiple compaction threads). But it should be ok.
Can you resubmit the patch for QA to kick in again? Thanks.
> 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,
> HBASE-9648-v1-trunk.patch, HBASE-9648.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 was sent by Atlassian JIRA
(v6.1.4#6159)
