Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
At present if edits file is corrupt namenode fails to start throwing EOFException as seen this this jira HADOOP-820. One way out in such cases was to remove offending entry from edits, but that is not straight forward as edits is a binary file. So, workaround was to ignore EOFException and continue with namenode startup. It would be good to have a tool to view edits entries or even modify it to a recoverable state.