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:02:52 GMT

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

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

      Description: 
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.

  was:
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.


    Fix Version/s:     (was: 2.3.0)
                   2.1.1-beta
         Assignee: Alejandro Abdelnur
          Summary: ContainerExistStatus should define a status for preempted containers  (was:
ContainerExistStatus and ContainerState are defined incorrectly)
    
> 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
>
>
> 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