[
https://issues.apache.org/jira/browse/YARN-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181187#comment-17181187
]
Steve Loughran commented on YARN-10396:
---------------------------------------
[~sunilg] This stops branch-3.2 (and presumably 3.1) from building.
Do you want revert/fix or shall I just revert for now?
And can fixes go through a Yetus build/test run next time, or at least a local
clean compile before the commit. Thanks
> Max applications calculation per queue disregards queue level settings in
> absolute mode
> ---------------------------------------------------------------------------------------
>
> Key: YARN-10396
> URL: https://issues.apache.org/jira/browse/YARN-10396
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
> Reporter: Benjamin Teke
> Assignee: Benjamin Teke
> Priority: Major
> Fix For: 3.2.2, 3.4.0, 3.3.1, 3.1.5
>
> Attachments: YARN-10396.001.patch, YARN-10396.002.patch,
> YARN-10396.003.patch
>
>
> Looking at the following code in
> {{org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue.java#L1126}}
> {code:java}
> int maxApplications = (int) (conf.getMaximumSystemApplications()
> * childQueue.getQueueCapacities().getAbsoluteCapacity(label));
> leafQueue.setMaxApplications(maxApplications);{code}
> In Absolute Resources mode setting the number of maximum applications on
> queue level gets overridden with the system level setting scaled down to the
> available resources. This means that the only way to set the maximum number
> of applications is to change the queue's resource pool. This line should
> consider the queue's
> {{yarn.scheduler.capacity.\{queuepath}.maximum-applications }}setting.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
