[
https://issues.apache.org/jira/browse/HDFS-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188723#comment-13188723
]
Yoram Arnon commented on HDFS-384:
----------------------------------
This should not be the default, and the example you give would be the wrong
time to use this option.
The system administrator would need to start the name node manually using this
special option, to ignore errors just this once, at her discretion.
All that said, this issue predates HDFS fsck.
Fsck obviates the need for this feature.
Yoram
> optionally ignore a bad entry in namenode state when starting up
> ----------------------------------------------------------------
>
> Key: HDFS-384
> URL: https://issues.apache.org/jira/browse/HDFS-384
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Yoram Arnon
> Assignee: Sameer Paranjpye
>
> if the namenode state (fsimage, edits) contains a bad entry, the namenode
> refused to start.
> Normally that's a good thing, alerting the administrator that something's
> corrupted.
> An option to ignore those entries is useful for recovering from such a
> condition. Anyone but a hard core developer would be helpless in the face of
> a corruption like that, and would prefer to lose a couple of records and be
> able to run than to be down, or remove the entire state of dfs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
