hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsuyoshi OZAWA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters
Date Thu, 05 Jun 2014 01:17:01 GMT

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

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

* Added isDefaultExitCode() method to {{ContainerImpl}} and updated to use it. ContainerImpl#exitCode
is initialized as ContainerExitStatus.INVALID already, so I did not change about that.
* Updated docs/comments like this:
{code}
+  /**
+   * Containers killed by AppMaster's issuing RPC(
+   * {@link org.apache.hadoop.yarn.api.ContainerManagementProtocol#
+   * stopContainers(org.apache.hadoop.yarn.api.protocolrecords.
+   * StopContainersRequest)}) explicitly.
+   */
+  public static final int KILL_AM_STOP_CONTAINER = -105;
+
+  /**
+   * Containers killed by ResourceManager's request or resync between
+   * ResourceManager and NodeManager.
+   */
+  public static final int KILL_BY_RESOURCEMANAGER = -106;
+
+  /**
+   * Containers killed by ResourceManager, due to accomplish of applications.
+   */
+  public static final int KILL_FINISHED_APPMASTER = -107;
{code}

[~bikassaha], please review it.

> 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
>         Attachments: YARN-2091.1.patch, YARN-2091.2.patch, YARN-2091.3.patch, YARN-2091.4.patch,
YARN-2091.5.patch, YARN-2091.6.patch, YARN-2091.7.patch
>
>
> 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)

Mime
View raw message