[
https://issues.apache.org/jira/browse/MAPREDUCE-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900317#comment-13900317
]
Hudson commented on MAPREDUCE-5746:
-----------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk #1672 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1672/])
MAPREDUCE-5746. Job diagnostics can implicate wrong task for a failed job.
(Jason Lowe via kasha) (kasha:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1567666)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/JobHistoryParser.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/TestJobHistoryParsing.java
> 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: 0.23.11, 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)
