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 2024/02/14 16:35:00 UTC

[jira] [Resolved] (YUNIKORN-2406) Recovered tasks do not move to Bound state

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

Craig Condit resolved YUNIKORN-2406.
------------------------------------
    Fix Version/s: 1.5.0
       Resolution: Fixed

Merged shim PR to master.

> Recovered tasks do not move to Bound state
> ------------------------------------------
>
>                 Key: YUNIKORN-2406
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2406
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler, shim - kubernetes
>            Reporter: Chia-Ping Tsai
>            Assignee: Craig Condit
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>
> The following events will update the count of allocated containers.
> 1. release allocation
> 2. schedule new allocation
> 3. remove a node
> Unfortunately, the event of recovering allocations does not update the count. Hence, the restarted scheduler shows zero value of allocated containers even though there are a bunch of running containers.
> This bug cause the restful API of showing container history will return zero, and so the dashboard of WEB UI shows zero also.



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