[
https://issues.apache.org/jira/browse/YUNIKORN-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-1623.
---------------------------------------------
Resolution: Duplicate
Moved this from the queue type change to the initialisation change.
Reason: if we initialise the system a queue might not exist any more for more
broad reasons than a queue type change. We need a generic solution as part of
the initialisation.
Marking this as duplicate of the more generic case of the init issue.
> Handle moved applications after recovery
> ----------------------------------------
>
> Key: YUNIKORN-1623
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1623
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
>
> If we move an application from any leaf to a special queue which exist for
> this purpose, we will encounter problems during recovery because the "queue"
> label/annotation still refers to a queue which have been converted since or
> removed.
> We either update these labels (which can put pressure on the API server and
> can also fail) or detect that we're dealing with recovered apps and act
> accordingly. The second seems to be a better option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
