[jira] [Commented] (YUNIKORN-468) Node resource updates should trigger cleanup

["Craig Condit (Jira)" <ji...@apache.org>]

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

Craig Condit commented on YUNIKORN-468:
---------------------------------------

[~manirajv06@gmail.com], [~wilfreds] can we close this as stale? I'm not sure this is needed any more and the old preemption code has been removed. 

I also don't think we need to worry about this as if there is truly pressure the kubelet will kill things off if need be. Additionally, our daemonset preemption logic will handle that case for us.

> Node resource updates should trigger cleanup
> --------------------------------------------
>
>                 Key: YUNIKORN-468
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-468
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - common
>            Reporter: Wilfred Spiegelenburg
>            Priority: Minor
>              Labels: pull-request-available
>
> Updating a node can set the overall size of a node and the resources allocated by a different scheduler (co-existence). The core just updates the node size and currently stops scheduling new resources even when the node is over subscribed.
> We should add a clean up in case that the node was shrunk and uses more than the resources available. the clean up should pre-empt enough resources to get it below the node size again.



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