You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2021/06/14 22:12:00 UTC
[jira] [Assigned] (YUNIKORN-676) App pending in one queue seems to
block app scheduling on the other queue
[ https://issues.apache.org/jira/browse/YUNIKORN-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weiwei Yang reassigned YUNIKORN-676:
------------------------------------
Assignee: Chaoran Yu
> App pending in one queue seems to block app scheduling on the other queue
> -------------------------------------------------------------------------
>
> Key: YUNIKORN-676
> URL: https://issues.apache.org/jira/browse/YUNIKORN-676
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler, shim - kubernetes
> Reporter: Weiwei Yang
> Assignee: Chaoran Yu
> Priority: Blocker
> Fix For: 0.11
>
> Attachments: queues.yaml, s1.yaml, s2.yaml, s3.yaml
>
>
> [~yuchaoran2011] found this issue on their cluster.
> It looks like when we have 2 queues, root.a and root.b, if we submit an app with invalid node constraints (e.g node affinity to some non-exist node) to root.a, the app will be pending (expected); however, in some cases, apps in root.b are blocked. Restarting the scheduler seems to be able to solve this. Root cause unclear yet, reproduction steps unclear as well at the moment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org