You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@yunikorn.apache.org by "Manikandan R (Jira)" <ji...@apache.org> on 2023/04/14 07:45:00 UTC

[jira] [Resolved] (YUNIKORN-1668) Check there must be one more limit setting for group with specific name defined in the config when use wildcard group limit

     [ https://issues.apache.org/jira/browse/YUNIKORN-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikandan R resolved YUNIKORN-1668.
------------------------------------
    Resolution: Fixed

> Check there must be one more limit setting for group with specific name defined in the config when use wildcard group limit
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YUNIKORN-1668
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1668
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: core - common
>            Reporter: Qi Zhu
>            Assignee: Qi Zhu
>            Priority: Major
>              Labels: pull-request-available
>
> Specifying a wildcard for the group limit sets a cumulative limit for all users in that queue. If there is no specific group mentioned the wildcard group limit would thus be the same as the queue limit. For that reason we do not allow specifying only one group limit that is using the wildcard. There must be at least one limit with a group name defined.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org