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:45:18 GMT

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

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

Actually as I stated in my last comment its 2 containers. So out of four 2 were started and
killed immediately and 2 were not started at all. So while I have to fix my problem of properly
counting how many containers were started vs finished/running, the real issue is that such
a major error condition is reported essentially as success. Basically if I didn't have a bug
on my end which made my AM hang, i would probably end up seeing SUCCEEDED in the RM console,
I am fixing it now and will follow up if I do see SUCCEEDED. But in any event its confusing
when it simply reports COMPLETED while describing a major error.

> 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