[
https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014284#comment-14014284
]
Bikas Saha commented on YARN-2091:
----------------------------------
We can check all cases of ContainerKillEvent and add new ExitStatus values
where it makes sense or use some good default value. If a test needs to change
to account for a new value then we should change the test. There may be other
cases of exit status being set or tested which are unrelated to container kill
event. Those can stay out of the scope of this jira.
> 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
>
>
> 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)
