[
https://issues.apache.org/jira/browse/YUNIKORN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123425#comment-17123425
]
Wilfred Spiegelenburg commented on YUNIKORN-193:
------------------------------------------------
I would see it more like this:
- only allowed on a parent queue (includes the root queue)
- limited to properties and resources
The reason I do not include the ACL is that ACLs are checked recursively. That
means the parent is checked for access if not set on the child. Specifying an
ACL on a generated queue would be the same as specifying it on the parent.
Even if there is a mixture of unmanaged and managed queues below a parent it
makes more sense to specify the ACL on just the managed queues. It does not
change what is possible but it makes it really clear what happens.
Proposed layout
{code:java}
queues:
- name: sandbox
parent: true
childtemplate:
properties:
application.sort.policy: fifo
resources:
guaranteed:
memory: 400000
vcore: 40000
max:
memory: 600000
vcore: 60000
{code}
> Add option to allow parent to set unmanaged child queue properties
> ------------------------------------------------------------------
>
> Key: YUNIKORN-193
> URL: https://issues.apache.org/jira/browse/YUNIKORN-193
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: core - scheduler
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Major
>
> The parent queue can not provide a template for auto generated child queues.
> This means that there is no way for a parent to specify an application
> sorting policy or a maximum resource setting on a child queue.
> - application sort policy
> - max resources
> We should allow a child template to be set on the managed parent queue (in
> the config) which can define the behaviour of leaf queues below it
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
