[
https://issues.apache.org/jira/browse/YUNIKORN-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755632#comment-17755632
]
Matt Poland commented on YUNIKORN-1921:
---------------------------------------
[~yangpoan] If two applications with differing PriorityClasses assigned (one
high-priority and another low-priority), are submitted at the same time, the
placeholders don't have any distinguishable way of guaranteeing the
high-priority job's placeholders get scheduled first, as capacity is made
available.
What we've seen is the lower priority jobs get their placeholders scheduled
first, leading to the lower-priority job running before the higher priority
job.
> Gang Scheduled Placeholder Pods Don't Inherit PriorityClasses
> -------------------------------------------------------------
>
> Key: YUNIKORN-1921
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1921
> Project: Apache YuniKorn
> Issue Type: Bug
> Reporter: Matt Poland
> Priority: Major
>
> While testing Yunikorn's gang scheduling feature, we noticed that placeholder
> pods do not inherit the PriorityClass defined for their associated pods
> awaiting scheduling.
> The placeholder pods are assigned a priority of 0 instead. This can affect
> jobs that are assigned a higher priority when they arrive around the same
> time as those of lower priority.
> Are there any plans to remedy this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
