Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 4 Apr 2012 23:22:23 +0000 (UTC)
From: "Todd Lipcon (Resolved) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1014908663.14808.1333581743191.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HDFS-1378) Edit log replay should track and
 report file offsets in case of errors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon resolved HDFS-1378.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.0

Committed backport to branch-1. Thanks, Colin!
                
> Edit log replay should track and report file offsets in case of errors
> ----------------------------------------------------------------------
>
>                 Key: HDFS-1378
>                 URL: https://issues.apache.org/jira/browse/HDFS-1378
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Colin Patrick McCabe
>             Fix For: 1.1.0, 0.23.0
>
>         Attachments: HDFS-1378-b1.002.patch, HDFS-1378-b1.003.patch, HDFS-1378-b1.004.patch, hdfs-1378-branch20.txt, hdfs-1378.0.patch, hdfs-1378.1.patch, hdfs-1378.2.txt
>
>
> Occasionally there are bugs or operational mistakes that result in corrupt edit logs which I end up having to repair by hand. In these cases it would be very handy to have the error message also print out the file offsets of the last several edit log opcodes so it's easier to find the right place to edit in the OP_INVALID marker. We could also use this facility to provide a rough estimate of how far along edit log replay the NN is during startup (handy when a 2NN has died and replay takes a while)

--
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