[
https://issues.apache.org/jira/browse/HDFS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079674#comment-13079674
]
Todd Lipcon commented on HDFS-2190:
-----------------------------------
hmm, how did the dir end up with an empty or malformed one? Any idea? Maybe we
should also address that problem (perhaps by backporting AtomicFileOutputStream
from trunk?)
> 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
>
>
> 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
