[
https://issues.apache.org/jira/browse/HADOOP-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635301#action_12635301
]
Hadoop QA commented on HADOOP-4079:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12391004/HADOOP-4079-2.patch
against trunk revision 699676.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3389/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3389/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3389/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3389/console
This message is automatically generated.
> Check for invalid queues in capacity scheduler
> ----------------------------------------------
>
> Key: HADOOP-4079
> URL: https://issues.apache.org/jira/browse/HADOOP-4079
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4079-1.patch, HADOOP-4079-2.patch
>
>
> The {{ResourceManagerConf}} class that is being moved to the capacity
> scheduler of HADOOP-3445 needs to check for a queue name that is not
> configured in the {{resource-manager-conf.xml}} file in its APIs and fail if
> it is not available. This feature was originally available, but due to
> subsequent changes in HADOOP-3698, queues are no longer being configured as
> part of the mentioned configuration file. Hence we need a different mechanism
> to check for valid queues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
