[
https://issues.apache.org/jira/browse/HDFS-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031837#comment-13031837
]
Aaron T. Myers commented on HDFS-1378:
--------------------------------------
All of the test failures except for {{TestEditLogFileOutputStream}} are known
to be failing on trunk. The {{TestEditLogFileOutputStream}} failure appears to
be transient. It passes on my box, and this is the message it failed with in
the Jenkins run:
{{noformat}}
java.net.BindException: Port in use: 0.0.0.0:50070
{{noformat}}
> 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: Aaron T. Myers
> Fix For: 0.23.0
>
> Attachments: hdfs-1378-branch20.txt, hdfs-1378.0.patch,
> hdfs-1378.1.patch
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
