hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5746) Job diagnostics can implicate wrong task for a failed job
Date Wed, 12 Feb 2014 16:10:21 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karthik Kambatla updated MAPREDUCE-5746:
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Just committed to trunk and branch-2.

[~jlowe] - wanted to commit to branch-0.23 as well, but didn't know how to handle the CHANGES.txt
for that. What do we do 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.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)

Mime
View raw message