[
https://issues.apache.org/jira/browse/MAPREDUCE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535323#comment-13535323
]
Hadoop QA commented on MAPREDUCE-4833:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12561562/MAPREDUCE4833-23.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3137//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3137//console
This message is automatically generated.
> Task can get stuck in FAIL_CONTAINER_CLEANUP
> --------------------------------------------
>
> Key: MAPREDUCE-4833
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4833
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster, mrv2
> Affects Versions: 0.23.5
> Reporter: Robert Joseph Evans
> Assignee: Robert Parker
> Priority: Critical
> Attachments: MAPREDUCE4833-23.patch
>
>
> If an NM goes down and the AM still tries to launch a container on it the
> ContainerLauncherImpl can get stuck in an RPC timeout. At the same time the
> RM may notice that the NM has gone away and inform the AM of this, this
> triggers a TA_FAILMSG. If the TA_FAILMSG arrives at the TaskAttemptImpl
> before the TA_CONTAINER_LAUNCH_FAILED message then the task attempt will try
> to kill the container, but the ContainerLauncherImpl will not send back a
> TA_CONTAINER_CLEANED event causing the attempt to be stuck.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
