hadoop-yarn-issues mailing list archives

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

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

Hadoop QA commented on YARN-75:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 1 new or modified test files.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    +1 core tests.  The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/31//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/31//console

This message is automatically generated.
> 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
>         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