[
https://issues.apache.org/jira/browse/YUNIKORN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit resolved YUNIKORN-2083.
------------------------------------
Fix Version/s: 1.4.0
Resolution: Fixed
Merged to master.
> Scheduler in standard mode should be able to handle pods with no
> applicationID defined
> --------------------------------------------------------------------------------------
>
> Key: YUNIKORN-2083
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2083
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> The scheduler in plugin mode can handle the case where a Pod is defined with
> schedulerName: yunikorn but no applicationID set can still be scheduled; it
> is treated as a non-YuniKorn pod and passed through the default scheduler
> logic.
> However, in the standard deployment mode we don't have any way to handle such
> pods, as there is no default scheduler embedded. Currently, these pods remain
> in Pending state but simply vanish from YuniKorn's perspective and are never
> scheduled, leading to subtle problems and difficult-to-diagnose issues.
> It would be useful if these pods could be scheduled anyway, ideally using the
> same algorithm for applicationID generation that the admission controller
> uses. This would make standalone yunikorn more useful as a default scheduler
> replacement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
