[
https://issues.apache.org/jira/browse/MAPREDUCE-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999009#comment-13999009
]
Hudson commented on MAPREDUCE-5888:
-----------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5605 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5605/])
MAPREDUCE-5888. Failed job leaves hung AM after it unregisters (Jason Lowe via
jeagles) (jeagles:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1594317)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/job/impl/JobImpl.java
> 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
> Fix For: 3.0.0, 2.5.0
>
> 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)
