[
https://issues.apache.org/jira/browse/MAPREDUCE-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-5746:
----------------------------------
Attachment: MAPREDUCE-5746-v2.branch-0.23.patch
Attaching a branch-0.23 version of the v2 patch since the original doesn't
apply cleanly to branch-0.23.
The 0.23.x section of CHANGES.txt is very wrong in trunk/branch-2 because it
hasn't been properly maintained. We do a lot of backporting of fixes to
branch-0.23, and it's a lot of noise to commit CHANGES.txt updates to trunk and
all the branch-2 flavors each time. So for now we update CHANGES.txt in
branch-0.23 manually when committing to branch-0.23.
> Job diagnostics can implicate wrong task for a failed job
> ---------------------------------------------------------
>
> Key: MAPREDUCE-5746
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5746
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 0.23.10, 2.1.1-beta
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Fix For: 2.4.0
>
> Attachments: MAPREDUCE-5746-v2.branch-0.23.patch,
> MAPREDUCE-5746-v2.patch, MAPREDUCE-5746.patch
>
>
> We've seen a number of cases where the history server is showing the wrong
> task as the reason a job failed. For example, "Task
> task_1383802699973_515536_m_027135 failed 1 times" when some other task had
> failed 4 times and was the real reason the job failed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
