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] [Updated] (HBASE-9648) collection one expired storefile causes it to be replaced by another expired storefile
Date Wed, 25 Sep 2013 15:08:03 GMT

     [ https://issues.apache.org/jira/browse/HBASE-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jean-Marc Spaggiari updated HBASE-9648:
---------------------------------------

    Status: Patch Available  (was: Open)

[~sershe], something like that? I'm not 100% sure it's required to loop over the storeFiles.
If they are ordered, then we can just pickup the last one... Same for the requests files.
But the idea is here. Wondering is this is what you had in minds. Triggering Hadoop QA in
the meantime to see if it works. 
                
> 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
>
>
> 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

Mime
View raw message