You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2021/08/02 08:38:00 UTC

[jira] [Commented] (YUNIKORN-772) Add AllocationAskUpdate in UpdateRequest

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

Wilfred Spiegelenburg commented on YUNIKORN-772:
------------------------------------------------

How does this fit in with:
 [https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#resources]

Specifically the third point:
{quote}Scheduling is done based on effective requests/limits, which means init containers can reserve resources for initialization that are not used during the life of the Pod.
{quote}

I do not think it can change we might need to look at the way we calculate the value in the shim but based on that remark it is NOT mutable.

> Add AllocationAskUpdate in UpdateRequest
> ----------------------------------------
>
>                 Key: YUNIKORN-772
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-772
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: scheduler-interface
>            Reporter: Chen Yu Teng
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: description.png
>
>
> When resource requirement changes in pod phase, shim will update locally and core-scheduler doesn't know it.
>  Web and core-scheduler shows resource requirement changed when pod phase transited from initialization to running state
> Any case?
>  This situation happens in YUNIKORN-706 .
>  Core-scheduler creates allocationAsk which is stable and calculated from containers.
>  If initcontainer resource requirements replace some containers requirements, core-scheduler will create allocationAsk and see it as fixed allocation and ignore resource requirement changed when pod phase transited from initialization to running state.
> !description.png|width=693,height=328!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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