hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-2471) Splitting logs, we'll make an output file though the region no longer exists
Date Wed, 03 Nov 2010 23:45:26 GMT

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

Jean-Daniel Cryans resolved HBASE-2471.

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Committed patch to trunk. It expect some sort of destabilization as some tests looked flaky
when I ran the full suite, so I might have to fix more tests in the near future.

> Splitting logs, we'll make an output file though the region no longer exists
> ----------------------------------------------------------------------------
>                 Key: HBASE-2471
>                 URL: https://issues.apache.org/jira/browse/HBASE-2471
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.90.0
>         Attachments: HBASE-2471-v2.patch
> The "human unit tester" (Kannan) last night wondered what happens splitting logs and
we come across an edit whose region has since been removed.  Taking a look, it looks like
we'll create the output file and write the edits for the no-longer-extant region anyways.
 This will leave litter in the filesystem -- region split files that will never be used nor
removed.  This issue is about verifying that indeed this is whats happening (We do SequenceFile.createWriter
with the overwrite flag set to true which tracing seems to mean create all intermediary directories
-- to be verified) and if it indeed is happening, fixing split so unless the region dir exists,
don't write out edits.. just drop them.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message