Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 6 Feb 2012 22:47:00 +0000 (UTC)
From: "Thomas Graves (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <398816037.4645.1328568420676.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1516551553.2262.1328541600354.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3816) capacity scheduler web ui bar
 graphs for used capacity wrong
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Graves updated MAPREDUCE-3816:
-------------------------------------

    Attachment: capschedulerFixedBarGraph.png

screenshot after changing usedCapacity to be defined as utilization was. This is similar to how 0.20.X or 1.0 has used capacity defined.
                
> 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
>         Attachments: 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