[
https://issues.apache.org/jira/browse/MAPREDUCE-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162327#comment-14162327
]
Hadoop QA commented on MAPREDUCE-4818:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673406/MAPREDUCE-4818.v4.patch
against trunk revision 2e789eb.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4940//console
This message is automatically generated.
> Easier identification of tasks that timeout during localization
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-4818
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4818
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mr-am
> Affects Versions: 0.23.3, 2.0.3-alpha
> Reporter: Jason Lowe
> Assignee: Siqi Li
> Labels: usability
> Attachments: MAPREDUCE-4818.v1.patch, MAPREDUCE-4818.v2.patch,
> MAPREDUCE-4818.v3.patch, MAPREDUCE-4818.v4.patch
>
>
> When a task is taking too long to localize and is killed by the AM due to
> task timeout, the job UI/history is not very helpful. The attempt simply
> lists a diagnostic stating it was killed due to timeout, but there are no
> logs for the attempt since it never actually got started. There are log
> messages on the NM that show the container never made it past localization by
> the time it was killed, but users often do not have access to those logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
