[
https://issues.apache.org/jira/browse/YUNIKORN-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730464#comment-17730464
]
Wilfred Spiegelenburg commented on YUNIKORN-1664:
-------------------------------------------------
Parent to leaf with an existing structure below the leaf is something we do not
want to allow. I think we need to explicitly prevent this from happening. If a
parent has one or more children do not allow the change.
The change could become hugely complex as there could be a huge multi level
queue structure below it. Handling all that is not simple.
I think we should only support this as a _stop_ of the queue structure and
{_}drain{_}. A _delete_ should already stop accepting new workloads in the
queue and let it {_}drain{_}. Maybe with a timeout and preempt the workloads
after some timeout.
We would really need to look at that as an extended use case.
> Handle parent->leaf conversion with running applications
> --------------------------------------------------------
>
> Key: YUNIKORN-1664
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1664
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
>
> Similarly to YUNIKORN-1566, whenever we change the queue from a parent to a
> leaf, we might need to move running applications from its child queues. Eg.:
> * queue is: root.dev.users.yunikorn with 3 running apps
> * root.dev becomes parent
> * apps in root.dev.users.yunikorn must be moved to a special dynamic queue
> where they can finish their execution
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
