[
https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014874#comment-14014874
]
Tsuyoshi OZAWA commented on YARN-2091:
--------------------------------------
Updated points:
* Introduced new exit code - KILL_EXCEEDED_VMEM, KILL_EXCEEDED_PME,
KILL_BY_APPMASTER, KILL_BY_RESOURCEMANAGER, KILL_FINISHED_APPMASTER. Naming and
type of error code are discussion points.
* Changed ContainerKillEvent to take ContainerExitStatus as one of
constructor's arguments.
* Removed isAMAware().
* Removed to call {{ContainerExitEvent.getExitCode()}} from
ContainerKilledTransition.
[~bikassaha], could you take a look?
> 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
>
>
> 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)
