You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2014/05/13 18:07:15 UTC

[jira] [Commented] (MAPREDUCE-5888) Failed job leaves hung AM after it unregisters

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996534#comment-13996534 ] 

Jason Lowe commented on MAPREDUCE-5888:
---------------------------------------

This was caused by MAPREDUCE-5317.  The ScheduledThreadPoolExecutor that was added was not marked to create daemon threads.

> 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
>
> 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)