You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2022/02/24 23:30:00 UTC
[jira] [Resolved] (YUNIKORN-1092) IsReservedOnNode() can match wrong node
[ https://issues.apache.org/jira/browse/YUNIKORN-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wilfred Spiegelenburg resolved YUNIKORN-1092.
---------------------------------------------
Fix Version/s: 1.0.0
Resolution: Fixed
> IsReservedOnNode() can match wrong node
> ---------------------------------------
>
> Key: YUNIKORN-1092
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1092
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Craig Condit
> Assignee: Wilfred Spiegelenburg
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> In scheduleer/objects/application.go, the IsReservedOnNode() function uses strings.HasPrefix to determine if a reservation belongs to a particular node. In the case where a node name is a prefix of another node (for example: node1 and node10), this can lead to application reservations stalling because the wrong node is chosen.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org