[jira] [Commented] (YUNIKORN-1929) Keep group tracker if it's from a specific limit to wildcard limit

["PoAn Yang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YUNIKORN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761291#comment-17761291 ] 

PoAn Yang commented on YUNIKORN-1929:
-------------------------------------

Hi [~mani], after reading [User Based Resource Usage Tracking in YuniKorn|https://docs.google.com/document/d/19FYOL1Uw7tSf74qyuVN40Fv-GdWd2KrBcHJpUQLTBZ4/edit#heading=h.ssab3bscccf2], I think you're right. Currently, group tracking is limited. We only track the first group which is defined in queue limit config. I will close my PR and this ticket. Thank you. Quota some content in the document for better reference:
{noformat}
The first point to define is that tracking can only occur against zero (0) or one (1) group. Usage can never be tracked against multiple groups. If a user is a member of multiple groups, a group is selected when the first usage is registered for the application. The group selected out of the list of groups in the UserGroup object to track against is based on the hierarchical queue limit configuration. The hierarchy is considered bottom up, starting from the leaf up to the root. The first group that is specified in the queue hierarchy for limiting usage that matches a group in the UserGroup object is selected for that application.

If no group limits are defined, in the hierarchy, usage is not tracked for a group. If no groups are defined in the UserGroup object no usage will be tracked against a group.

The tracker considers only the group received as part of the UserGroup object at the time of first usage registration for the application in the tracker. In case of group changes while the user’s application is actively being tracked, the tracker does not consider the group change. However, If the user submits a new application, the most current group information at that point in time will be used.{noformat}

> 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
>             Fix For: 1.4.0
>
>
> 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: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org