[
https://issues.apache.org/jira/browse/MAPREDUCE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167769#comment-13167769
]
Hadoop QA commented on MAPREDUCE-3328:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505380/MAPREDUCE-3328.trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 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 (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1423//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1423//console
This message is automatically generated.
> mapred queue -list output inconsistent and missing child queues
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-3328
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3328
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Thomas Graves
> Assignee: Ravi Prakash
> Priority: Critical
> Attachments: MAPREDUCE-3328.branch-0.23.patch,
> MAPREDUCE-3328.trunk.patch, MAPREDUCE-3328.trunk.patch,
> MAPREDUCE-3328.trunk.patch
>
>
> When running mapred queue -list on a 0.23.0 cluster with capacity scheduler
> configured with child queues. In my case I have queues default, test1, and
> test2. test1 has subqueues of a1, a2. test2 has subqueues of a3 and a4.
> - the child queues do not show up
> - The output of maximum capacity doesn't match the format of the current
> capacity and capacity. the latter two use float while the maximum is
> specified as int:
> Queue Name : default
> Queue State : running
> Scheduling Info : queueName: "default", capacity: 0.7, maximumCapacity: 90.0,
> currentCapacity: 0.0, state: Q_RUNNING,
> ======================
> Queue Name : test
> Queue State : running
> Scheduling Info : queueName: "test", capacity: 0.2, maximumCapacity: -1.0,
> currentCapacity: 0.0, state: Q_RUNNING,
> ======================
> Queue Name : test2
> Queue State : running
> Scheduling Info : queueName: "test2", capacity: 0.1, maximumCapacity: 5.0,
> currentCapacity: 0.0, state: Q_RUNNING,
> ======================
> here default is configured to have capacity=70% and maximum capacity = 90%
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
