[jira] [Resolved] (YUNIKORN-1451) required node preemptor should use IsPreempted field

["Wilfred Spiegelenburg (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YUNIKORN-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wilfred Spiegelenburg resolved YUNIKORN-1451.
---------------------------------------------
    Fix Version/s: 1.2.0
       Resolution: Fixed

Change committed, victim selection now excludes allocation that are already marked as being preempted.
Thank you [~samhxwu]

> required node preemptor should use IsPreempted field
> ----------------------------------------------------
>
>                 Key: YUNIKORN-1451
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1451
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wu hsuang zong
>            Priority: Minor
>              Labels: newbie, pull-request-available
>             Fix For: 1.2.0
>
>
> Allocations can be preempted and are marked as being preempted already.
> The {{PreemptionContext.filterAllocations()}} call does not check if the allocation is already being preempted. It might thus consider it again as being pre-emptable during a second check.
> We should exclude allocations already being preempted from the list of victims.
> The impact should be limited at this point as we cannot have two reservations trigger preemption at the moment.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org