hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-75) RMContainer should handle a RELEASE event while RUNNING
Date Fri, 07 Sep 2012 01:46:08 GMT

    [ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450260#comment-13450260

Hudson commented on YARN-75:

Integrated in Hadoop-Mapreduce-trunk-Commit #2724 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2724/])
    YARN-75. Missing test. Ugh. (Revision 1381811)

     Result = FAILURE
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381811
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java

> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>                 Key: YARN-75
>                 URL: https://issues.apache.org/jira/browse/YARN-75
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.0-alpha
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>             Fix For: 2.1.0-alpha
>         Attachments: YARN-75_2.txt, YARN-75.txt
> An AppMaster can send a container release at any point. Currently this results in an
exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show
up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this
set being complete. 

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

View raw message