[ 
https://issues.apache.org/jira/browse/YARN-10590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Gyori updated YARN-10590:
--------------------------------
    Summary: Fix legacy auto queue creation absolute resource calculation loss  
(was: Fix TestCapacitySchedulerAutoCreatedQueueBase with related absolute 
calculation loss)

> Fix legacy auto queue creation absolute resource calculation loss
> -----------------------------------------------------------------
>
>                 Key: YARN-10590
>                 URL: https://issues.apache.org/jira/browse/YARN-10590
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Qi Zhu
>            Assignee: Qi Zhu
>            Priority: Major
>         Attachments: YARN-10590.001.patch, YARN-10590.002.patch
>
>
> "Because as we discussed in YARN-10504 , the initialization of auto created 
> queues from template was changed (see comment and comment)."
> 1. As the comment we discussed, we found the effective core is different(the 
> gap), because the update effective  will override the absolute auto created 
> leaf queue.
> 2. But actually, the new logic in YARN-10504 override is right, the 
> difference is caused by test case , don't consider the calculation loss of 
> multi resource type, the cap/absolute are all calculated by one type, 
> (memory) in DefaultResourceCalculator, (dominant type) in 
> DominantResourceCalculator. As we known in the comment, the absolute auto 
> created leaf queue will merge the effective resource by cap/absolute 
> calculated result, this caused the gap.
> 2. In other case(not absolute case) in the auto created leaf queue, the merge 
> will not cause the gap, in update effective resource override will also use 
> the one type calculated result. 
> 3. So this jira just make the test right, the calculation result is already 
> right.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to