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

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

[jira] [Resolved] (YUNIKORN-1395) Account for preempted placeholder in the placeholder data

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

Craig Condit resolved YUNIKORN-1395.
------------------------------------
    Fix Version/s: 1.2.0
       Resolution: Fixed

Merged to master.

> Account for preempted placeholder in the placeholder data
> ---------------------------------------------------------
>
>                 Key: YUNIKORN-1395
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1395
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler
>    Affects Versions: 1.1.0
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.2.0
>
>
> If we pre-empt a placeholder to make room for a daemon set pod we do not update the counter inside the application placeholder data object.
> After the pre-emption it shows as a placeholder that should be there but is no longer on the system.
> When we replace or timeout a placeholder we do account for it correctly.
> We directly call {{app.RemoveAllocation(uuid)}} from the partition code. We do not take into account the account the termination type there which we should to make sure we account correctly for the preemption in the data.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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