[
https://issues.apache.org/jira/browse/YUNIKORN-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860751#comment-17860751
]
Wilfred Spiegelenburg commented on YUNIKORN-2703:
-------------------------------------------------
Before we start breaking things in different ways lets not push this in hastily
in 1.5.2. Lets keep that release for the last dead lock fix and the current
issues and figure this out correctly in 1.6.0 which is only weeks away any way.
> Scheduler does not honor default queue setting from the ConfigMap
> -----------------------------------------------------------------
>
> Key: YUNIKORN-2703
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2703
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Mit Desai
> Assignee: Mit Desai
> Priority: Major
>
> YUNIKORN-1650 added an override for default queue name in the config map to
> solve for the scenario where the provided placement rule is evaluated before
> other rules.
> Scheduler also adds a default queue if the pod labels or annotations does not
> define a queue name. Because this happens before the placement rules are
> evaluated, we end up in the same situation of applications getting placed in
> the default queue and ignoring all other placement rules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
