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

Hadoop QA commented on YARN-333:
--------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12587744/YARN-333-2.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 2 new 
or modified test files.

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

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
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/1235//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1235//console

This message is automatically generated.
                
> Schedulers cannot control the queue-name of an application
> ----------------------------------------------------------
>
>                 Key: YARN-333
>                 URL: https://issues.apache.org/jira/browse/YARN-333
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: YARN-333-1.patch, YARN-333-2.patch, YARN-333.patch
>
>
> Currently, if an app is submitted without a queue, RMAppManager sets the 
> RMApp's queue to "default".
> A scheduler may wish to make its own decision on which queue to place an app 
> in if none is specified. For example, when the fair scheduler 
> user-as-default-queue config option is set to true, and an app is submitted 
> with no queue specified, the fair scheduler should assign the app to a queue 
> with the user's name.

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