You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Xiaobao Wu (Jira)" <ji...@apache.org> on 2024/10/29 06:19:00 UTC

[jira] [Resolved] (YUNIKORN-2933) Don't add duplicated taskGroup to app

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

Xiaobao Wu resolved YUNIKORN-2933.
----------------------------------
    Resolution: Not A Bug

> Don't add duplicated taskGroup to app
> -------------------------------------
>
>                 Key: YUNIKORN-2933
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2933
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>    Affects Versions: 1.3.0, 1.5.2
>            Reporter: Xiaobao Wu
>            Priority: Minor
>              Labels: pull-request-available
>
>     When the app processes the _yunikorn.apache.org/task-groups_ annotation on Pod, it did not consider the case of taskgroup with the same name (i.e. taskgroup with the same {*}name{*}).For example, the following task-groups information is defined:
>  
> {code:java}
> yunikorn.apache.org/task-groups='
> [{
>         "name": "spark-executor",
>         "minMember": 2,
>         "minResource": {
>             "cpu": "1",
>             "memory": "1Gi"
>         }
>     }, {
>         "name": "spark-driver",
>         "minMember": 1,
>         "minResource": {
>             "cpu": "1",
>             "memory": "1Gi"
>         }
>     },
>     {
>         "name": "spark-executor",
>         "minMember": 1,
>         "minResource": {
>             "cpu": "2",
>             "memory": "2Gi"
>         }
>     }
> ]
> '{code}
>     From the above example, it can be seen that there are two task-group with *the same name* in the task-groups. So, after these ph Tasks are created, if an executor task (2C 2G)
> try to allocate placeholder‘s resource, it may erroneously release the ph task in the *spark-executor* group with a resource specification of 1C 1G (because the resource specification cannot meet 2C 2G). In this regard, I think that before properly handling ph tasks with different resource specifications within the same task group, it is necessary to avoid having two task-group with the same name but different resource specifications in the app.
>  



--
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