Tsuyoshi OZAWA commented on YARN-2091:

Found that it's simple enough adding methods like isAMAware() to 
public class ContainerExitStatus {

  public static boolean isAMAware(int exitReason) {
    return (exitReason == DISKS_FAILED)
        || (exitReason == KILL_EXCEEDED_PMEM)
        || (exitReason == KILL_EXCEEDED_VMEM);
I try to leave ContainerExitStatus just a class not enum for now. Please let me 
know if you have suggestions about this.

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

Reply via email to