You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Aaron T. Myers (JIRA)" <ji...@apache.org> on 2011/08/05 01:14:27 UTC
[jira] [Updated] (HDFS-2190) NN fails to start if it encounters an
empty or malformed fstime file
[ https://issues.apache.org/jira/browse/HDFS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron T. Myers updated HDFS-2190:
---------------------------------
Attachment: hdfs-2190.0.patch
Patch which addresses the issue. I also took the liberty of removing the vestigial {{FSImage.getTimeFiles}} method.
> 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