[
https://issues.apache.org/jira/browse/YUNIKORN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398390#comment-17398390
]
Wilfred Spiegelenburg commented on YUNIKORN-193:
------------------------------------------------
{quote}I prefer to keep compatibility. If there is a template, we use it and
ignore all old behavior (properties, resources and limit.maxapplications).
Otherwise, we keep old behavior.
{quote}
that sounds good and from an implementation perspective that means we process
using the old behaviour first logging when we add the attribute and then
overlay that with the new behaviour.
> 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: Chia-Ping Tsai
> Priority: Major
> Labels: pull-request-available
>
> 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]
