hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-117) SecondaryNameNode: should not throw exception and exit if only one makedir failure
Date Sun, 25 Apr 2010 19:45:50 GMT

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

Jakob Homan updated HDFS-117:
-----------------------------

    Status: Open  (was: Patch Available)

Canceling patch. No longer applies by a long shot. There have been quite a few changes to
the SNN since this patch's last revision; we should see if this is still a problem.  

> SecondaryNameNode:  should not throw exception and exit if only one makedir failure
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-117
>                 URL: https://issues.apache.org/jira/browse/HDFS-117
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Wang Xu
>            Assignee: Wang Xu
>         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.


Mime
View raw message