[ https://issues.apache.org/jira/browse/YARN-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177800#comment-17177800 ]
Benjamin Teke commented on YARN-10396: -------------------------------------- Uploaded a new patch with the checkstyle issues fixed. The test issue seems unrelated. > 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 > 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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org