hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wang Xu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-85) FSEditLog.open should stop going on if cannot open any directory
Date Mon, 07 Dec 2009 14:37:18 GMT

    [ https://issues.apache.org/jira/browse/HDFS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786929#action_12786929
] 

Wang Xu commented on HDFS-85:
-----------------------------

Hi Jakob, what should I do next? Upload another patch? 
(The patch had only been made to 0.19 branch and tested in our environment.)

> FSEditLog.open should stop going on if cannot open any directory
> ----------------------------------------------------------------
>
>                 Key: HDFS-85
>                 URL: https://issues.apache.org/jira/browse/HDFS-85
>             Project: Hadoop HDFS
>          Issue Type: Bug
>         Environment: CentOS 5.2, jdk 1.6, hadoop 0.19.1
>            Reporter: Wang Xu
>            Assignee: Wang Xu
>         Attachments: fseditlog-open.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> FSEditLog.open will be invoked when SecondaryNameNode doCheckPoint,
> If no dir is opened successfully, it only prints some WARN messages in log,
> and goes on running. 
> However, it causes the editStreams becomes empty and cannot by synced 
> in. And if editStreams were decreased to 0 when exceptions occured during
> logsync, NameNode would print FATAL log message and halt itself. Hence,
> we think it should also stopped itself at that time.

-- 
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