[
https://issues.apache.org/jira/browse/HADOOP-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-5392:
-------------------------------
Attachment: HADOOP-5392-v2.1.patch
Attaching a patch the fixes the issue. Added a test case to validate that.
Result of test-patch
{code}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
{code}
> JobTracker crashes during recovery if job files are garbled
> -----------------------------------------------------------
>
> Key: HADOOP-5392
> URL: https://issues.apache.org/jira/browse/HADOOP-5392
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-5392-v2.1.patch
>
>
> Jobtracker crashed in the recovery stage for a job with 0 byte job.xml.
> Ideally one would expect the jobtracker to try and recover as many jobs as
> possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
