[
https://issues.apache.org/jira/browse/HDFS-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219444#comment-13219444
]
Hudson commented on HDFS-2992:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #1883 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1883/])
HDFS-2992. Edit log failure trace should include transaction ID of error.
Contributed by Colin Patrick McCabe (Revision 1295227)
Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1295227
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogLoader.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSEditLogLoader.java
> 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
