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 Fri, 30 May 2014 16:17:02 GMT

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

Tsuyoshi OZAWA commented on YARN-2091:

Changelogs in v4:
* Updated ContainersMonitorImpl for dispatching KILL_EXCEEDED_VMEM/KILL_EXCEEDED_PMEM.
* If the exit reason is AM-aware({{ContainerExitStatus#isAMAware()}}), pass it to app masters.
Otherwise, the exit reason is converted into ExitCode.TERMINATED.getExitCode() for backward
compatibility. AM-Aware events are DISKS_FAILED, KILL_EXCEEDED_PMEM, KILL_EXCEEDED_VMEM currently.

> 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

View raw message