[
https://issues.apache.org/jira/browse/YUNIKORN-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864018#comment-17864018
]
Wilfred Spiegelenburg commented on YUNIKORN-2689:
-------------------------------------------------
I think this has been fixed in YUNIKORN-2527 for queues that are configured in
the configmap, i.e. managed queues, the state will be reset. For dynamic queues
we should not have a state that is important. That Jira was only fixed recently
and will only be part of the 1.6 release.
> 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]
