[
https://issues.apache.org/jira/browse/YARN-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761832#comment-13761832
]
Hudson commented on YARN-1049:
------------------------------
SUCCESS: Integrated in Hadoop-Hdfs-trunk #1517 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1517/])
YARN-1049. ContainerExistStatus should define a status for preempted
containers. (tucu) (tucu:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1521036)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/records/ContainerExitStatus.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestSchedulerUtils.java
> 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
