hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tao Yang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
Date Fri, 19 Oct 2018 09:34:00 GMT
Tao Yang created YARN-8917:
------------------------------

             Summary: 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


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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org


Mime
View raw message