[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656890#comment-16656890 ]
Sunil Govindan commented on YARN-8917: -------------------------------------- [~Tao Yang] cud u pls write a test case to prove the calculation is wrong in level+3 queues. That will help to really see the problem in tests and easy to understand. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > ----------------------------------------------------------------------------------------- > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler > Affects Versions: 3.2.1 > Reporter: Tao Yang > Assignee: Tao Yang > Priority: Major > Attachments: YARN-8917.001.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org