[
https://issues.apache.org/jira/browse/YUNIKORN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg updated YUNIKORN-1793:
--------------------------------------------
Description:
If the placement rules change loading an already running workload might fail.
Similar case exists for queue that no longer exist in the config. Even if the
queue exists the type could have changed from leaf to parent etc.
Running workloads should never be rejected during init. If a placement fails
the application should be placed in a temporary queue. This needs to be
restricted to workloads during init only and a queue should be used that cannot
be created via the configuration or placement rules.
was:
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.
> Handle placement rule and queue changes during initialisation
> -------------------------------------------------------------
>
> 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 loading an already running workload might fail.
> Similar case exists for queue that no longer exist in the config. Even if the
> queue exists the type could have changed from leaf to parent etc.
> Running workloads should never be rejected during init. If a placement fails
> the application should be placed in a temporary queue. This needs to be
> restricted to workloads during init 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]
