[jira] [Commented] (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:comment-tabpanel=17460785#comment-17460785 ] Tamas Domok commented on YARN-11033: Hi [~snemeth], Sure. Here is the PR for the branch-3.3 : [GitHub Pull Request #3808|https://github.com/apache/hadoop/pull/3808]. For the branch-3.2 the backport is not needed, because the property is not there yet. > 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 > > Time Spent: 2h 10m > 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-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (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:comment-tabpanel=17457165#comment-17457165 ] Szilard Nemeth commented on YARN-11033: --- Hi [~tdomok], Just committed your patch to trunk. Could you please check whether it's required to backport this to branch-3.3 / branch-3.2? Thanks. > 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 > > Time Spent: 2h > 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-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
