Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 27 Feb 2012 19:12:47 +0000 (UTC)
From: "Colin Patrick McCabe (Updated) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <626777256.24073.1330369967466.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1275382125.7760.1329963110510.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-2992) Edit log failure trace should include
 transaction ID of error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Colin Patrick McCabe updated HDFS-2992:
---------------------------------------

    Attachment: HDFS-2992.patch

The edit log failure trace now includes the transaction ID of the error.
                
> Edit log failure trace should include transaction ID of error
> -------------------------------------------------------------
>
>                 Key: HDFS-2992
>                 URL: https://issues.apache.org/jira/browse/HDFS-2992
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>              Labels: newbie
>         Attachments: HDFS-2992.patch
>
>
> Currently, if there is an exception reading edits, it tells the operator the offset of the error, but not the transaction ID. This makes it difficult to correlate against the output of the OEV, for example.

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