[
https://issues.apache.org/jira/browse/YUNIKORN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit updated YUNIKORN-796:
----------------------------------
Fix Version/s: 1.0.0
> 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
> Fix For: 1.0.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
