hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1049) ContainerExistStatus should define a status for preempted containers
Date Fri, 06 Sep 2013 12:04:52 GMT

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

Alejandro Abdelnur updated YARN-1049:
-------------------------------------

    Attachment: YARN-1049.patch
    
> ContainerExistStatus should define a status for preempted containers
> --------------------------------------------------------------------
>
>                 Key: YARN-1049
>                 URL: https://issues.apache.org/jira/browse/YARN-1049
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0-beta
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 2.1.1-beta
>
>         Attachments: YARN-1049.patch
>
>
> With the current behavior is impossible to determine if a container has been preempted
or lost due to a NM crash.
> Adding a PREEMPTED exit status (-102) will help an AM determine that a container has
been preempted.
> Note the change of scope from the original summary/description. The original scope proposed
API/behavior changes. Because we are passed 2.1.0-beta I'm reducing the scope of this JIRA.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message