Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0EADBF506 for ; Fri, 25 Apr 2014 17:51:58 +0000 (UTC) Received: (qmail 61685 invoked by uid 500); 25 Apr 2014 17:51:50 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 61612 invoked by uid 500); 25 Apr 2014 17:51:49 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 61374 invoked by uid 99); 25 Apr 2014 17:51:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Apr 2014 17:51:45 +0000 Date: Fri, 25 Apr 2014 17:51:45 +0000 (UTC) From: "Jason Lowe (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1985) YARN issues wrong state when "running beyond virtual memory limits" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)