[
https://issues.apache.org/jira/browse/YUNIKORN-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit resolved YUNIKORN-3003.
------------------------------------
Fix Version/s: 1.7.0
1.6.1
Resolution: Fixed
Merged to master and cherry-picked to branch-1.6.
> Previously preempted allocations can be preempted again
> -------------------------------------------------------
>
> Key: YUNIKORN-3003
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3003
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Paul Santa Clara
> Assignee: Paul Santa Clara
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0, 1.6.1
>
>
> This is particularly apparent when preemption is used with longer values of
> terminationGracePeriodSeconds. A task can be selected for preemption and
> during it's gracefulshutdown period, that same task can again be preempted.
> When this occurs, the preemptingResource for the impacted queue will again be
> incremented for the SAME task preventing it from ever reaching zero again
> even after all tasks have fully completed their termination and notified the
> core scheduler. After stopping all workloads, the preemptingResource will
> remain positive unless the yunikorn scheduler pod is restarted
> ```
> {color:#1d1c1d} "preemptingResource": \{ "ephemeral-storage": 21474836480,
> "memory": 4194304000, "pods": 1, "vcore": 1000 },{color}
> ```
> This preemptingResource leak, in turn, may convince the scheduler to avoid
> future preemptions when it attempts to use it to compute the actual used
> resources for a given queue:
> [https://github.com/apache/yunikorn-core/blob/v1.6.0/pkg/scheduler/objects/preemption.go#L826]
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
