[
https://issues.apache.org/jira/browse/HADOOP-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680382#action_12680382
]
Devaraj Das commented on HADOOP-5392:
-------------------------------------
+1 on the patch. Please ensure that "ant test" goes through with the patch.
BTW while reviewing this patch, I noticed that the JobHistory calls use the
user's jobconf to create/read history file paths on both
hadoop.job.history.location and hadoop.job.history.user.location. This should
be fixed (in a separate jira) to use the JobTracker's conf for the history
files on hadoop.job.history.location.
> 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, HADOOP-5392-v2.3.patch,
> HADOOP-5392-v2.6.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.
