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

Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2023/03/14 02:26:00 UTC

[jira] [Resolved] (YUNIKORN-1559) rethink QOS BestEffort pod scheduling

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

Wilfred Spiegelenburg resolved YUNIKORN-1559.
---------------------------------------------
    Fix Version/s: 1.3.0
       Resolution: Implemented

This will be fixed as part of the changes for YUNIKORN-1632

> rethink QOS BestEffort pod scheduling
> -------------------------------------
>
>                 Key: YUNIKORN-1559
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1559
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - scheduler, shim - kubernetes
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Qi Zhu
>            Priority: Major
>             Fix For: 1.3.0
>
>
> The best effort pods on K8s do not request resources. The default scheduler will just dump them on a node and hope for the best.
> In YuniKorn we need resources to schedule a pod. We reject a pod without a request set. As a default we assign 1M memory to the pod to make sure it gets scheduled. 1 byte would be better, need to rethink how we do this.
> This also affects other BestEffort pod resource calculations
>  * init containers
>  * pod overhead 



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