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:07:00 UTC
[jira] [Commented] (YUNIKORN-1242) gang: delay in scheduling after using all placeholders
[ https://issues.apache.org/jira/browse/YUNIKORN-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557224#comment-17557224 ]
Wilfred Spiegelenburg commented on YUNIKORN-1242:
-------------------------------------------------
Fix the logic in tryAllocate and check if there are still candidates for replacement available
> gang: delay in scheduling after using all placeholders
> ------------------------------------------------------
>
> Key: YUNIKORN-1242
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1242
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - common
> Affects Versions: 0.10
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Critical
> Labels: pull-request-available
>
> The check in the normal allocation {{Application.tryAllocate()}} does not take into account that there can be multiple types of gang definitions. Which triggers weird behaviour if you either request more instances of a gang member than there are defined or there is a mismatch between the placeholder and the real allocation size.
> Requirement is to have at least 2 gang types defined with placeholders and 1 of those has all its placeholder exhausted and the other is not.
> This causes the pod for the gang type that has exhausted its placeholders to be delayed for scheduling until the other gang type's placeholder time out.
>
--
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