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

Hadoop QA commented on YARN-289:
--------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12579624/YARN-289.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 5 
warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

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

This message is automatically generated.
                
> Fair scheduler allows reservations that won't fit on node
> ---------------------------------------------------------
>
>                 Key: YARN-289
>                 URL: https://issues.apache.org/jira/browse/YARN-289
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: YARN-289.patch
>
>
> An application requests a container with 1024 MB.  It then requests a 
> container with 2048 MB.  A node shows up with 1024 MB available.  Even if the 
> application is the only one running, neither request will be scheduled on it.

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

Reply via email to