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

Posted to dev@yunikorn.apache.org by "Chaoran Yu (Jira)" <ji...@apache.org> on 2021/12/21 02:11:00 UTC

[jira] [Resolved] (YUNIKORN-796) Pod scheduling could disproportionately concentrate on one node

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

Chaoran Yu resolved YUNIKORN-796.
---------------------------------
      Assignee: Chaoran Yu
    Resolution: Cannot Reproduce

Resolving as Cannot Reproduce for now because I haven't seen this symptom for some time now. I'll either re-open it or create another one with more details if it happens again

> Pod scheduling could disproportionately concentrate on one node
> ---------------------------------------------------------------
>
>                 Key: YUNIKORN-796
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-796
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler
>            Reporter: Chaoran Yu
>            Assignee: Chaoran Yu
>            Priority: Major
>
> We've observed a few cases when YK keeps scheduling incoming pods to just one node, even though the cluster has many other nodes that have abundant resources. Not sure what could be causing this behavior because we don't see it in every K8s cluster we have. Maybe somewhere in the node sorting algorithm, a node could be favored over all other nodes under some conditions?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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