[
https://issues.apache.org/jira/browse/YUNIKORN-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685326#comment-17685326
]
Peter Bacsko commented on YUNIKORN-1546:
----------------------------------------
Thanks for the reply [~wilfreds].
{quote}
We need to define what is more important: config or running applications and
children in memory. Config seems to be the one that should overrule the current
in running setup. That means we need to define what we do with the current
running applications if we change a leaf to a parent. What do we do with the
leafs under a parent and all the applications that run in those leafs? Do we
move the structure out of the way to allow the configuration change to be
applied...
{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?
I'll create some subtasks to the best of my knowledge and we can refine them
later.
> 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: [email protected]
For additional commands, e-mail: [email protected]
