You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2009/05/06 20:44:30 UTC

[jira] Issue Comment Edited: (HADOOP-3717) Provide tool to view/change edits file

    [ https://issues.apache.org/jira/browse/HADOOP-3717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706552#action_12706552 ] 

Jakob Homan edited comment on HADOOP-3717 at 5/6/09 11:44 AM:
--------------------------------------------------------------

Linking to HADOOP-915, which has definitely gone stale now, but is still a duplication.

      was (Author: jghoman):
    This code has definitely gone stale now.
  
> Provide tool to view/change edits file
> --------------------------------------
>
>                 Key: HADOOP-3717
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3717
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>    Affects Versions: 0.19.0
>            Reporter: Lohit Vijayarenu
>
> 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. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.