hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2471) Splitting logs, we'll make an output file though the region no longer exists
Date Tue, 20 Apr 2010 18:30:50 GMT

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

Todd Lipcon commented on HBASE-2471:

Good point, I was thinking that pre-split the region would be flushed, and thus the logs would
be expired. But the logs could have records for other unflushed regions.

> 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: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.20.5, 0.21.0
> 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