Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 28 May 2014 00:32:02 +0000 (UTC)
From: "Tsuyoshi OZAWA (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12715856.1400707136559.28028.1401237122072@arcas>
In-Reply-To: <JIRA.12715856.1400707136559@arcas>
References: <JIRA.12715856.1400707136559@arcas>
Subject: [jira] [Commented] (YARN-2091) Add
 ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsuyoshi OZAWA commented on YARN-2091:
--------------------------------------

ContainerManagerImpl cannot distinguish the exit reason because ContainersMonitorImpl dispatches ContainerKillEvent without the exit reason currently. I plan to add exit reason to ContainerKillEvent. Please let me know if you have better idea.

> Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters
> -----------------------------------------------------------------------
>
>                 Key: YARN-2091
>                 URL: https://issues.apache.org/jira/browse/YARN-2091
>             Project: Hadoop YARN
>          Issue Type: Task
>            Reporter: Bikas Saha
>            Assignee: Tsuyoshi OZAWA
>
> Currently, the AM cannot programmatically determine if the task was killed due to using excessive memory. The NM kills it without passing this information in the container status back to the RM. So the AM cannot take any action here. The jira tracks adding this exit status and passing it from the NM to the RM and then the AM. In general, there may be other such actions taken by YARN that are currently opaque to the AM. 


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