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

Sunil G updated YARN-4304:
--------------------------
    Attachment: 0002-YARN-4304.patch

Attaching updated  version of patch addressing the comments.

- {{getAccessibleNodeLabels}}  can  have "*". hence in case when its ANY, we 
need to consider cluster labels (we can try see what all labels are having 
resources in that queue at that time). Patch contains this change
- It seems there was an existing bug in showing capacities for REST api 
{{/ws/v1/cluster/scheduler}} o/p when labels were enabled. Currently it shows 
only default label. Changes in {{CapacitySchedulerQueueInfo}}. I handled this  
fix also here, if needed I can spin to another ticket as its for nodelabels for 
general case. pls advise.

[~leftnoteasy] could you please help to check the patch.

> AM max resource configuration per partition to be displayed/updated correctly 
> in UI and in various partition related metrics
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4304
>                 URL: https://issues.apache.org/jira/browse/YARN-4304
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: webapp
>    Affects Versions: 2.7.1
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-4304.patch, 0002-YARN-4304.patch, 
> REST_and_UI.zip
>
>
> As we are supporting per-partition level max AM resource percentage 
> configuration, UI and various metrics also need to display correct 
> configurations related to same. 
> For eg: Current UI still shows am-resource percentage per queue level. This 
> is to be updated correctly when label config is used.
> - Display max-am-percentage per-partition in Scheduler UI (label also) and in 
> ClusterMetrics page
> - Update queue/partition related metrics w.r.t per-partition 
> am-resource-percentage



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to