You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2025/02/19 23:02:00 UTC

[jira] [Closed] (YUNIKORN-2213) Handle Allocation allocation id during recovery properly

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

Craig Condit closed YUNIKORN-2213.
----------------------------------
    Resolution: Delivered

No longer relevant after the ask / allocation merge.

> Handle Allocation allocation id during recovery properly
> --------------------------------------------------------
>
>                 Key: YUNIKORN-2213
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2213
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - scheduler
>            Reporter: Manikandan R
>            Assignee: Manikandan R
>            Priority: Major
>
> As a part of recovery, Allocation allocationID modifies to same allocationID with different suffix no (incremented by 1). For example, alloc-0 to alloc-1. After YUNIKORN-2204, we are seeing this behaviour. Need to handle this properly based on the discussion at  https://github.com/apache/yunikorn-core/pull/740#discussion_r1408666888



--
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