[
https://issues.apache.org/jira/browse/YUNIKORN-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797980#comment-17797980
]
Wilfred Spiegelenburg commented on YUNIKORN-2258:
-------------------------------------------------
This is a legal setup. A zero for maxapplications should be ignored as it will
not be set in the system. It is also impossible to distinguish between a 0 and
not being part of the config with the parsing we do. So any 0 values should be
ignored by the validator.
Also setting a zero does not make sense as it blocks the whole queue.
> align the behavior of undefined maxapplications with resources
> --------------------------------------------------------------
>
> Key: YUNIKORN-2258
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2258
> Project: Apache YuniKorn
> Issue Type: Wish
> Reporter: Chia-Ping Tsai
> Assignee: Vinayak Hegde
> Priority: Major
>
> The following config is invalid since the undefined `maxapplications` of
> child queue is considered be zero. It means all leaf queues must define
> `maxapplications` if parent has `maxapplications`.
>
> {code:java}
> partitions:
> - name: default
> queues:
> - name: root
> parent: true
> submitacl: "*"
> maxapplications: 2
> queues:
> - name: child {code}
>
>
> In contrast, the resources has no such requirements. We can leave undefined
> resources for leaf queues. For example:
>
> {code:java}
> partitions:
> - name: default
> queues:
> - name: root
> parent: true
> submitacl: "*"
> queues:
> - name: parent
> resources:
> max:
> memory: 20G
> vcore: 20
> queues:
> - name: child {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
