hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1985) YARN issues wrong state when "running beyond virtual memory limits"
Date Fri, 25 Apr 2014 17:51:45 GMT

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

Jason Lowe commented on YARN-1985:
----------------------------------

There are only three states for a container: NEW, RUNNING, or COMPLETED.  Note that COMPLETED
does not imply success rather that the container is no longer running.  In order to discern
success or failure from a completed container one must examine the exit code of the container
(i.e.: the ContainerStatus#getExitStatus method).

Are both containers running over their memory limits or is only one running over and somehow
both are being killed?  That's where the RM/NM logs would help.

> YARN issues wrong state when "running beyond virtual memory limits"
> -------------------------------------------------------------------
>
>                 Key: YARN-1985
>                 URL: https://issues.apache.org/jira/browse/YARN-1985
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.3.0
>            Reporter: Oleg Zhurakousky
>
> When deploying YARN application with multiple containers and AM determines that the resource
limits been reached (e.g., virtual memory) it starts killing *all* containers while reporting
a *single* COMPLETED status essentially hanging AM waiting for more containers to report its
state.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message