hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-167) AM stuck in KILL_WAIT for days
Date Wed, 24 Oct 2012 17:28:13 GMT

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

Robert Joseph Evans commented on YARN-167:

Yes it looks very much like this can also happen in branch-2, and trunk.  I also wanted to
mention that the stack traces showed more or less nothing.  All of the threads were waiting
on I/O or event queues. Nothing was actually processing any data or deadlocked holding some
> AM stuck in KILL_WAIT for days
> ------------------------------
>                 Key: YARN-167
>                 URL: https://issues.apache.org/jira/browse/YARN-167
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 0.23.3
>            Reporter: Ravi Prakash
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: TaskAttemptStateGraph.jpg
> We found some jobs were stuck in KILL_WAIT for days on end. The RM shows them as RUNNING.
When you go to the AM, it shows it in the KILL_WAIT state, and a few maps running. All these
maps were scheduled on nodes which are now in the RM's Lost nodes list. The running maps are

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

View raw message