[
https://issues.apache.org/jira/browse/YUNIKORN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741820#comment-17741820
]
Wilfred Spiegelenburg commented on YUNIKORN-1793:
-------------------------------------------------
We first need to revamp the K8shim side to separate out the allocations from
the nodes and change the ordering of what we do. We can then add this handling
on top of those changes.
With that change in the init we can communicate without keeping state that the
k8shim is working through the initialisation state.
> 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]
