[
https://issues.apache.org/jira/browse/YUNIKORN-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101672#comment-18101672
]
Wilfred Spiegelenburg commented on YUNIKORN-3320:
-------------------------------------------------
I think we need to take a step back: {{tryReservedAllocate()}} did get fixed
for the required node release. It did not get fixed for the reservation release
count.
I think we need to use this Jira to add the test only, update the description
to match. File a new Jira to fix {{tryReservedAllocate()}} in the same way as
we did for other functions in YUNIKORN-3319 introduced a callback that can be
used for that in this case and in YUNIKORN-3319. We should file a new Jira to
fix updating the reservation counter at the partition level.
> tryReservedAllocate can release required node reservations
> ----------------------------------------------------------
>
> Key: YUNIKORN-3320
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3320
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Affects Versions: 1.9.0
> Reporter: Wilfred Spiegelenburg
> Assignee: KAI-JAY TU
> Priority: Major
> Labels: newbie, pull-request-available
>
> {{tryReservedAllocate}} cleans up reservations that should not be on the node
> any more: reservation is older than the {{reservationWaitTimeout}}. This does
> not take into account that there might be other required node reservations on
> that same node.
> Required node reservations should not be released from a node even if they
> are older than the timeout
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
