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

Posted to issues@yunikorn.apache.org by "Yongjun Zhang (Jira)" <ji...@apache.org> on 2023/10/13 22:34:00 UTC

[jira] [Commented] (YUNIKORN-1993) Race between allocation removal and Completed state change

    [ https://issues.apache.org/jira/browse/YUNIKORN-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775084#comment-17775084 ] 

Yongjun Zhang commented on YUNIKORN-1993:
-----------------------------------------

Hi [~wilfreds]

Thanks a lot for the analysis and fix.

Hopefully this will resolve the issue reported in YUNIKORN-1996 (we are testing out). What about YUNIKORN-1985? It may be a similar one.

 

> Race between allocation removal and Completed state change
> ----------------------------------------------------------
>
>                 Key: YUNIKORN-1993
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1993
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>
> A race between go routines exists that can leave allocation tracked on a queue. The end result could show a queue that has allocation without any running applications in the queue.
> Worst case scenario would be an exhausted root queue quota causing all scheduling to stop.



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