You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2023/02/07 22:38:00 UTC

[jira] [Commented] (YUNIKORN-1546) [Umbrella] Allow changing queue type: parent to leaf and back

    [ https://issues.apache.org/jira/browse/YUNIKORN-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685602#comment-17685602 ] 

Wilfred Spiegelenburg commented on YUNIKORN-1546:
-------------------------------------------------

{quote}This reminds me the recovery scenario in YARN/FS. I believe the solution (which, I think was yours) is that running applications for which no queue can be determined are moved to a queue named "root.recovery". Maybe we can do something similar during leaf->parent conversion, like moving them under a queue named "root.preserved". Question is, do we apply some resource limits to this queue, and if so, what limits?
{quote}
That was my solution in YARN. Ii think we need a similar solution in YuniKorn.

Resource limits: setting an artificial limit is going to be tricky. The queue should never get any new applications after the recovery. I think we need to let it run without a limit. We even need to think about preemption of those applications and allocations..

> [Umbrella] Allow changing queue type: parent to leaf and back
> -------------------------------------------------------------
>
>                 Key: YUNIKORN-1546
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1546
>             Project: Apache YuniKorn
>          Issue Type: New Feature
>          Components: core - common
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Peter Bacsko
>            Priority: Major
>         Attachments: TestUpdateQueues2.patch
>
>
> In certain cases we would like to allow changing the queue type from a parent to a leaf or the other way around in one update.
> Currently there is no way to change the type and it will throw an error when tried. That means two updates need to be made to first remove and then add the same queue with a different type. This is only important for managed queues, i.e. queues in the config. Dynamic queues should not allow type changes as they are removed when empty.
>  * parent to leaf: only if no children are registered for the parent
>  * leaf to parent: only of no applications are running in the queue



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org