[
https://issues.apache.org/jira/browse/YARN-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046225#comment-15046225
]
Sunil G commented on YARN-4418:
-------------------------------
Thank you [~leftnoteasy] for clarifying the scenario.
I still have one doubt here, {{getAMResourceLimitPerPartition}} will try to get
the Queue's current usage (it can use more than allocated capacity) in case
when no labels are configured. It can happen in case where some more containers
got allocated rather than some new application. In this case
{{getAMResourceLimitPerPartition}} wont be invoked and if we calcuate the
AMLimit at this time, it will be lil higher (since queue is running top of its
allocated capcity, going towards max-capcity).
This was the only corner case which I felt, other than that all cases are
handled as you mentioned. So I could try only to get NO_LABEL partition from
DAO side? Do you see this as a valid case. pls share your thoughts.
> AM Resource Limit per partition can be updated to ResourceUsage as well
> -----------------------------------------------------------------------
>
> Key: YARN-4418
> URL: https://issues.apache.org/jira/browse/YARN-4418
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.7.1
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-YARN-4418.patch, 0002-YARN-4418.patch
>
>
> AMResourceLimit is now extended to all partitions after YARN-3216. Its also
> better to track this ResourceLimit in existing {{ResourceUsage}} so that REST
> framework can be benefited to avail this information easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
