[
https://issues.apache.org/jira/browse/YUNIKORN-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864030#comment-17864030
]
Wilfred Spiegelenburg edited comment on YUNIKORN-2689 at 7/9/24 6:54 AM:
-------------------------------------------------------------------------
This might need an update for dynamic queues that were created below the
managed queue.They would not get reset with the current fix.
Example for a dynamic queue: root.parent.<namespace>.<user>
Placement rules:
* User
** Tag for namespace
*** fixed root.parent
Remove the queue root.parent and all queues below will be marked as draining.
When we add root.parent back we should reset the state of all dynamic queues
below it to make YUNIKORN-2688 possible. We should *not* change the queues
below parent that are managed
was (Author: wifreds):
This might need an update for dynamic queues that were created below the
managed queue.They would not get reset with the current fix.
> transition draining queues back to active if they are added back
> ----------------------------------------------------------------
>
> Key: YUNIKORN-2689
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2689
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Hengzhe Guo
> Assignee: Hengzhe Guo
> Priority: Minor
>
> When a queue is removed but still has jobs running in it, it will be in
> 'draining' state. At this stage, if the queue is added back, we should expect
> the queue to be transitioned back to active state. However, such transition
> is not found in the code base. We observed a case where a queue removed and
> soon added back eventually ended up deleted after all jobs were drained.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
