[jira] Commented: (HBASE-2471) Splitting logs, we'll make an output file though the region no longer exists

["stack (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-2471:
------------------------------

Should be easy fix.  From j-d "If regiondir does not exist, do not create a recovered.edits file... skip"... In split logs need to keep a list of non-existent regions tooo...  so we don't check fs for each encountered edit.

> 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
>             Fix For: 0.90.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.