hadoop-hdfs-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] (HDFS-2190) NN fails to start if it encounters an empty or malformed fstime file
Date Mon, 08 Aug 2011 21:42:27 GMT

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

Todd Lipcon commented on HDFS-2190:
-----------------------------------

Aaron pointed out offline that we already treat non-existent fstime files like this. So, a
truncated one should be treated the same as the non-existent one.

So, +1.

> NN fails to start if it encounters an empty or malformed fstime file
> --------------------------------------------------------------------
>
>                 Key: HDFS-2190
>                 URL: https://issues.apache.org/jira/browse/HDFS-2190
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.20.203.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>         Attachments: hdfs-2190.0.patch, hdfs-2190.1.patch
>
>
> On startup, the NN reads the fstime file of all the configured dfs.name.dirs to determine
which one to load. However, if any of the searched directories contain an empty or malformed
fstime file, the NN will fail to start. The NN should be able to just proceed with starting
and ignore the directory containing the bad fstime file.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message