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] [Updated] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters
Date Thu, 29 May 2014 00:30:05 GMT

     [ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tsuyoshi OZAWA updated YARN-2091:
---------------------------------

    Attachment: YARN-2091.1.patch

Added ContainerExitStatus.KILL_EXCEEDED_MEMORY and test to pass the exit status from NM to
RM correctly.

> 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
>
>
> 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