[
https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026206#comment-15026206
]
Sunil G commented on YARN-4304:
-------------------------------
Thanks Naga for the comments.
bq. 1.In the web page Max application(AM) resources for a user and queue should
it not be at partition if mentioned per partition ?
Scheduler UI displays queue inside each partition. So these resources will be
per-queue per-partition. Hence we need not have to change label explicitly
stating per-partition. Make sense?
bq. Web rendering code formatting might not be needed
Yes, I also thought so earlier before doing that. But i think some times its
becoming difficult when u need add a line which cross 80 lines limit. I can
change back old way if its the general view.
bq. existing bug in showing capacities for REST api /ws/v1/cluster/scheduler
o/p when labels were enabled.
As of now if we see REST o/p for {{scheduler}} when used with labels, we can
easily see usedCapacity is 0 (also others capacities). If its kept for default
label , we need to make changes in variable name atleast else it will give a
wrong meaning and wrong o/p. Yes, for cases where labels are not configured,
this breaks compatibility.
I think I will segregate that issue from this and will raise a new ticket
because this ticket is getting focusing on multiple issues. And all related
discussions for this can be moved there. Will file a new ticket shortly.
> 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)