hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5888) Failed job leaves hung AM after it unregisters
Date Wed, 14 May 2014 23:12:36 GMT

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

Hudson commented on MAPREDUCE-5888:

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1779 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1779/])
MAPREDUCE-5888. Failed job leaves hung AM after it unregisters (Jason Lowe via jeagles) (jeagles:
* /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

View raw message