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 2022/06/22 04:24:00 UTC

[jira] [Updated] (YUNIKORN-1246) tryAllocate: required node issues

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

Wilfred Spiegelenburg updated YUNIKORN-1246:
--------------------------------------------
    Summary: tryAllocate: required node issues  (was: tryAllocate:)

> tryAllocate: required node issues
> ---------------------------------
>
>                 Key: YUNIKORN-1246
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1246
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - common
>    Affects Versions: 1.1.0
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Major
>
> When an ask has a required node set we only try to allocate the one specific node. In tryAllocate we have two issues:
>  * The node specified as the required node might not exist. In that case the scheduler crashes with a nil pointer
>  * If the release of a preempted allocation is processed during the scheduling cycle we might try to allocate the ask on the node via the normal tryAllocate and not use the tryReservedAllocate flow. If that happens we leave the node reserved forever and that makes the node unusable.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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