You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Szilard Nemeth (Jira)" <ji...@apache.org> on 2022/03/02 13:47:00 UTC
[jira] [Resolved] (YARN-11033) isAbsoluteResource is not correct for dynamically created queues
[ https://issues.apache.org/jira/browse/YARN-11033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Szilard Nemeth resolved YARN-11033.
-----------------------------------
Hadoop Flags: Reviewed
Resolution: Fixed
> isAbsoluteResource is not correct for dynamically created queues
> ----------------------------------------------------------------
>
> Key: YARN-11033
> URL: https://issues.apache.org/jira/browse/YARN-11033
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Affects Versions: 3.4.0
> Reporter: Tamas Domok
> Assignee: Tamas Domok
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.3
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> The property *isAbsoluteResource* was added in YARN-10237 to the scheduler response, it uses pattern matching on the capacity configuration value, but for dynamically created queues (using legacy AQC) the capacity configuration is not available like that.
> The *AbstractCSQueue.getCapacityConfigType()* can be used to determine whether it is absolute resource or not.
> The *isAbsoluteResource* property was not added to the root queue, that should be fixed for consistency too. E.g.: the *mode* property is added for the root and for other queues too.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org