[
https://issues.apache.org/jira/browse/YUNIKORN-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101666#comment-18101666
]
Wilfred Spiegelenburg commented on YUNIKORN-3319:
-------------------------------------------------
With the introduction of the callback in YUNIKORN-3321 on the application:
{{reservationReleasedCallback}} this issue can be fixed in a similar way. The
application has the callback and it can be used from {{TryPreemption()}} as
long as locking allows it.
Changing this to a newbie Jira based on that change
> Reservations released by preemption not tracked
> -----------------------------------------------
>
> Key: YUNIKORN-3319
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3319
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Affects Versions: 1.8.0
> Reporter: Wilfred Spiegelenburg
> Priority: Critical
>
> During preemption we release old non node requires reservations. These
> releases are made even if we do not preempt. The number of released
> reservations is not accounted for at the partition level.
> TryPreemption needs to return the released reservations in all cases even if
> there is not preemption that happens. This could be an "empty" allocation
> result that just account for the released reservations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
