You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2013/08/27 23:40:21 UTC

[jira] [Updated] (YARN-1049) ContainerExistStatus and ContainerState are defined incorrectly

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

Arun C Murthy updated YARN-1049:
--------------------------------

    Fix Version/s:     (was: 2.1.0-beta)
                   2.3.0
    
> ContainerExistStatus and ContainerState are defined incorrectly
> ---------------------------------------------------------------
>
>                 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
>            Priority: Blocker
>             Fix For: 2.3.0
>
>
> ContainerExitStatus defines a few constant with special exit status values (0,-1000, -100, -101). This is incorrect, we should not define any special constants and limit to return the actual process exist status code.
> ContainerState should include PREEMPTED (when preempted by YARN), LOST (when the NM crashes).
> With the current behavior is impossible to determine if a container has been preempted or lost due to a NM crash.
> Marking it as a blocker for 2.1.0 as this is an API/behavior change.

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