hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marc Spaggiari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9648) collection one expired storefile causes it to be replaced by another expired storefile
Date Sat, 07 Dec 2013 12:41:35 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842202#comment-13842202
] 

Jean-Marc Spaggiari commented on HBASE-9648:
--------------------------------------------

So. Back on this JIRA ;)

I think patch HBASE-9648-v1-trunk.patch can fix this issue the user faced on the mailing list.
 It basically do what need to be done to avoid this from the first level.

It passed Hadoop QA, but I can also port it to 0.94 and give it a bigger try on my own cluster...

> 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)

Mime
View raw message