[jira] [Resolved] (YUNIKORN-287) ask release can cause multiple reservations to be released

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

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

Wilfred Spiegelenburg resolved YUNIKORN-287.
--------------------------------------------
    Resolution: Fixed

shim changes committed, all done

> ask release can cause multiple reservations to be released
> ----------------------------------------------------------
>
>                 Key: YUNIKORN-287
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-287
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.9
>
>
> complex scenario with multiple things going on:
> - one application with multiple pending requests
> - two or more pending requests are reserved
> - one of those reserved pending requests is being allocated (scheduler is done, cache confirm is called async)
> - the request being allocated is cancelled by the shim in between the time the scheduler is done and the cache confirms
> The cancellation of the shim triggers an update and the cache update triggers an update. These two updates cause counters for the number of reservations to be decremented twice.
> The side effect is that the node that is reserved by the ask that is not removed will be skipped until that ask is allocated on a different node. If that takes a while (waiting for scale up for instance) then there will be an impact on scheduling.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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