optionally ignore a bad entry in namenode state when starting up
----------------------------------------------------------------
Key: HADOOP-443
URL: http://issues.apache.org/jira/browse/HADOOP-443
Project: Hadoop
Issue Type: Improvement
Reporter: Yoram Arnon
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 contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
