[
https://issues.apache.org/jira/browse/YARN-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840892#comment-13840892
]
Hadoop QA commented on YARN-807:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12617311/YARN-807-4.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 4 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-tools/hadoop-sls
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/2609//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2609//console
This message is automatically generated.
> When querying apps by queue, iterating over all apps is inefficient and
> limiting
> ---------------------------------------------------------------------------------
>
> Key: YARN-807
> URL: https://issues.apache.org/jira/browse/YARN-807
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.0.4-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-807-1.patch, YARN-807-2.patch, YARN-807-3.patch,
> YARN-807-4.patch, YARN-807.patch
>
>
> The question "which apps are in queue x" can be asked via the RM REST APIs,
> through the ClientRMService, and through the command line. In all these
> cases, the question is answered by scanning through every RMApp and filtering
> by the app's queue name.
> All schedulers maintain a mapping of queues to applications. I think it
> would make more sense to ask the schedulers which applications are in a given
> queue. This is what was done in MR1. This would also have the advantage of
> allowing a parent queue to return all the applications on leaf queues under
> it, and allow queue name aliases, as in the way that "root.default" and
> "default" refer to the same queue in the fair scheduler.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
