[
https://issues.apache.org/jira/browse/YUNIKORN-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-3360.
---------------------------------------------
Fix Version/s: 1.10.0
Resolution: Fixed
As a safety check make sure the allocation is still part of the request map.
This allows simpler checks down the stack when cleaning up asks as all callers
now confirm the key is present in the request map.
change committed to master
> RollbackAllocation should safety check request existence
> ---------------------------------------------------------
>
> Key: YUNIKORN-3360
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3360
> Project: Apache YuniKorn
> Issue Type: Task
> Components: core - scheduler
> Reporter: Wilfred Spiegelenburg
> Assignee: Aditya Maheshwari
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
>
> When RollbackAllocation is called the only check that is made is for the
> existence in the allocations map. There should be a check against the
> requests map also to make sure the allocation is looked at.
> The ask should always be there but we need to be consistent with other code
> paths which do this check.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
