[
https://issues.apache.org/jira/browse/YUNIKORN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730439#comment-17730439
]
Peter Bacsko edited comment on YUNIKORN-1793 at 6/8/23 8:08 AM:
----------------------------------------------------------------
This is similar to the issue I also noticed while working on YUNIKORN-1566. I
also created a JIRA for the issue: YUNIKORN-1623. Since then, I have moved to
other tasks so this is pending.
We have to make sure that we don't accidentally solve this twice.
was (Author: pbacsko):
This is similar to the issue I also noticed while working on YUNIKORN-1566. I
also created a JIRA for the issue: YUNIKORN-1623. Since then, I have moved to
other tasks so this is pending.
I think the "preserved" logic might be re-usable here, at least partly (see
Draft PR https://github.com/apache/yunikorn-core/pull/502).
> Handle placement rule changes during recovery
> ---------------------------------------------
>
> Key: YUNIKORN-1793
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1793
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - common
> Reporter: Wilfred Spiegelenburg
> Priority: Major
>
> If the placement rules change a recovery of a running workload might fail.
> Running workloads should never be rejected during recovery. If a placement
> fails the application should be placed in a temporary queue. This needs to be
> restricted to recovered workloads only and a queue should be used that cannot
> be created via the configuration or placement rules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
