[
https://issues.apache.org/jira/browse/AMBARI-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043906#comment-14043906
]
Hars Vardhan commented on AMBARI-6088:
--------------------------------------
The issue with this approach ( % = allocated * 100 / (allocated + available) )
is -- if queue's allocated resource exceeds the given Capacity, the metric will
always show 100%.
For example, a 'default' queue has 'Absolute Capacity' = 5%, 'Absolute Max
Capacity' = 30%, Total Yarn Memory = 100GB.
When 'Absolute Used Capacity' = 2.5GB, available = 2.5GB ==> % = (2.5 *
100)/ (2.5+2.5) = 50% ^Alright
When 'Absolute Used Capacity' = 5GB, available = 0 ==> % = (5 *
100)/ (5+0) = 100% ^Alright
When 'Absolute Used Capacity' = 6GB, available =0 ==> % = (6 *
100)/ (6+0) = 100% ?
When 'Absolute Used Capacity' = 30GB, available =0 ==> % = (30 *
100)/ (30+0) = 100% ?
Note: I used YARN's resource manager web UI terminology.
> Ambari-web's YARN Metric "Queue Memory Used" is not meaningful
> --------------------------------------------------------------
>
> Key: AMBARI-6088
> URL: https://issues.apache.org/jira/browse/AMBARI-6088
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.5.1, 1.6.0, 1.6.1
> Reporter: Hars Vardhan
> Labels: patch
> Fix For: 1.6.1
>
> Attachments: AMBARI-6088.patch
>
>
> On this webUI : http://<ambari-host-name>:8080/#/main/services/YARN/summary
> "Queue Memory Used" graph in Ambari' YARN web page seems abnormal. Sometimes,
> queue is using more than 400% of the cluster memory!! How this is calculated?
> It doesn't match with any metrics shown on Resource Manager UI page.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
