[jira] Issue Comment Edited: (HADOOP-5730) SecondaryNameNode: should not throw exception and exit if only one makedir failure

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

    [ https://issues.apache.org/jira/browse/HADOOP-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704152#action_12704152 ] 

Wang Xu edited comment on HADOOP-5730 at 4/29/09 8:21 AM:
----------------------------------------------------------

Hi Konstantin,

I updated the patch to fix the above issue.

However, I do not satisfy with it yet:  if an exception is throwed, the checkpointing will be interrupted and the former closed editStreams of FSEditLog in SecondaryNameNode.startCheckpoint() would never be re-open again. 

Any suggestion?

      was (Author: gnawux):
    I updated the patch to fix the above issue.

However, I do not satisfy with it yet:  if an exception is throwed, the checkpointing will be interrupted and the former closed editStreams of FSEditLog in SecondaryNameNode.startCheckpoint() would never be re-open again. 

Any suggestion?
  
> SecondaryNameNode:  should not throw exception and exit if only one makedir failure
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-5730
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5730
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.19.1
>            Reporter: Wang Xu
>            Assignee: Wang Xu
>             Fix For: 0.19.2
>
>         Attachments: secondarynamenode-startcp.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> In CheckpointStorage.startCheckPointing(), if one mkdir failed, it 
> will throw an exception and exit. 
> However, because the editlog has been closed before, the editStreams
> of FSEditLog of NameNode will becomes empty as a result, which
> will affect any further logSync operations.
> Hence we think it should only print  WARN message instead of 
> throw the exception

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