[
https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bilwa S T updated YARN-10260:
-----------------------------
Comment: was deleted
(was: [~jhung] Thanks for raising this issue
Instead of throwing exception when configstate is RUNNING and currentState is
DRAINING, we can activateQueue() . Thoughts?)
> Allow transitioning queue from DRAINING to RUNNING state
> --------------------------------------------------------
>
> Key: YARN-10260
> URL: https://issues.apache.org/jira/browse/YARN-10260
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Jonathan Hung
> Assignee: Bilwa S T
> Priority: Major
>
> We found in our cluster, a queue was erroneously stopped. Then queue is
> internally in DRAINING state. It cannot be moved back to RUNNING state until
> the queue is finished draining. For queues with large workloads, this can
> block other apps from submitting to this queue for a long time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
