You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/12/04 19:54:35 UTC
[jira] [Commented] (HBASE-9648) collection one expired storefile
causes it to be replaced by another expired storefile
[ https://issues.apache.org/jira/browse/HBASE-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839201#comment-13839201 ]
Sergey Shelukhin commented on HBASE-9648:
-----------------------------------------
stumbled upon this jira (not bug :)) again... do you want to go with either patch
> 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#6144)