[
https://issues.apache.org/jira/browse/MAPREDUCE-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996732#comment-13996732
]
Hadoop QA commented on MAPREDUCE-5888:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12644640/MAPREDUCE-5888.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}. There were no new javadoc 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/4599//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4599//console
This message is automatically generated.
> Failed job leaves hung AM after it unregisters
> -----------------------------------------------
>
> Key: MAPREDUCE-5888
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5888
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am
> Affects Versions: 2.2.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-5888.patch
>
>
> When a job fails the AM hangs during shutdown. A non-daemon thread pool
> executor thread prevents the JVM teardown from completing, and the AM lingers
> on the cluster for the AM expiry interval in the FINISHING state until
> eventually the RM expires it and kills the container. If application limits
> on the queue are relatively low (e.g.: small queue or small cluster) this can
> cause unnecessary delays in resource scheduling on the cluster.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
