[
https://issues.apache.org/jira/browse/YARN-10922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Domok resolved YARN-10922.
--------------------------------
Resolution: Won't Do
I opened a separate Jira:
YARN-11069 - Dynamic Queue ACL handling in Legacy and Flexible Auto Created
Queues
> Investigation: Verify if legacy AQC works as documented
> -------------------------------------------------------
>
> Key: YARN-10922
> URL: https://issues.apache.org/jira/browse/YARN-10922
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Szilard Nemeth
> Assignee: Tamas Domok
> Priority: Minor
> Labels: pull-request-available
> Attachments: capacity-scheduler.xml
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Quoting from the Capacity Scheduler documentation:
> https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html
> Section: "Dynamic Auto-Creation and Management of Leaf Queues"
> The task is to verify if legacy AQC works like this:
> {quote}
> The parent queue which has been enabled for auto leaf queue creation,
> supports the configuration of template parameters for automatic configuration
> of the auto-created leaf queues. The auto-created queues support all of the
> leaf queue configuration parameters except for Queue ACL, Absolute Resource
> configurations. Queue ACLs are currently inherited from the parent queue i.e
> they are not configurable on the leaf queue template
> {quote}
--
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
