You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "PoAn Yang (Jira)" <ji...@apache.org> on 2023/09/01 12:01:00 UTC
[jira] [Closed] (YUNIKORN-1929) Keep group tracker if it's from a specific limit to wildcard limit
[ https://issues.apache.org/jira/browse/YUNIKORN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
PoAn Yang closed YUNIKORN-1929.
-------------------------------
Fix Version/s: (was: 1.4.0)
Target Version: (was: 1.4.0)
Resolution: Won't Do
> Keep group tracker if it's from a specific limit to wildcard limit
> ------------------------------------------------------------------
>
> Key: YUNIKORN-1929
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1929
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: PoAn Yang
> Assignee: PoAn Yang
> Priority: Major
> Labels: pull-request-available
>
> Currently, the user/group manager can't pass the following case:
> 1. Create a queue with the following limits:
>
> {noformat}
> limits:
> - limit: "specific groups"
> groups:
> - group1
> - group2
> maxresources:
> memory: 100
> vcores: 100
> maxapplications: 2
> - limit: "wildcard"
> groups:
> - *
> maxresources:
> memory: 50
> vcores: 50
> maxapplications: 1{noformat}
> 2. Increase resource usage (memory: 50, vcores: 50) for group1 and group2.
> 3. Remove "group2" from the "specific groups" limit and update the config. The "group2" tracker will be removed.
> 4. If we increase resource usage again, the system will pass. However, at this moment, the real resource usage is 100 memory/vocres and it's more than the wildcard limit.
>
--
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