[
https://issues.apache.org/jira/browse/MAPREDUCE-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218589#comment-13218589
]
Hadoop QA commented on MAPREDUCE-3816:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12516378/MAPREDUCE-3816.patch
against trunk revision .
+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 eclipse:eclipse. The patch built with eclipse:eclipse.
+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/1953//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1953//console
This message is automatically generated.
> capacity scheduler web ui bar graphs for used capacity wrong
> ------------------------------------------------------------
>
> Key: MAPREDUCE-3816
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3816
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Priority: Critical
> Fix For: 0.23.2
>
> Attachments: MAPREDUCE-3816.patch, MAPREDUCE-3816.patch,
> MAPREDUCE-3816.patch, MAPREDUCE-3816.patch, MAPREDUCE-3816.patch,
> capacityschedabsoluteCapacities.png, capacityschedulerusedcap.png,
> capschedulerFixedBarGraph.png
>
>
> The capacity scheduler web ui has bar graphs showing the capacity/used
> capacity/max capacity for each queue. The used capacity it is showing is
> actually the % of its parents queue it is using, which doesn't make sense on
> the bar graphs when compared to the capacity and max capacity of that
> particular queue. The bar graphs should be using utilization so that the
> user can see that its using x% or the y% allocated to that queue.
> I will attach some screen shots showing the issue.
--
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
