hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Zhurakousky (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:33:15 GMT

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

Oleg Zhurakousky commented on YARN-1985:
----------------------------------------

Actually, the 4 COMPLETE reports are log duplication, so it is actually two. The other two
containers didn't even start. Which is fine, but the real issue is that while its clearly
an ERROR condition it reports is as simple COMPLETE.

> 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