[
https://issues.apache.org/jira/browse/HDFS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081206#comment-13081206
]
Todd Lipcon commented on HDFS-2190:
-----------------------------------
hm, the change to fix this possible failure seems good. I'm a little nervous
about charging on through the missing files at startup. Have you worked through
the various conditions where this might be the case? Is there any time when it
would be preferable to fail to start up, and make the user manually choose
which storage dir to start from?
Maybe we should just add a config here that the user can use to acknowledge the
corruption and move forward? See HDFS-2079
> 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
