You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2014/02/07 21:56:22 UTC

[jira] [Updated] (MAPREDUCE-5746) Job diagnostics can implicate wrong task for a failed job

     [ 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.patch

Simple patch to report the first task that failed rather than the last.  Needs a test case.

> 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
>         Attachments: 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)