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

Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2022/11/18 17:22:00 UTC

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

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

Craig Condit resolved YUNIKORN-468.
-----------------------------------
    Resolution: Abandoned

Closing as abandoned.

> 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