[
https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated YARN-10260:
------------------------------
Component/s: capacity scheduler
Hadoop Flags: Reviewed
Target Version/s: 3.3.1, 2.10.1, 3.2.2, 3.4.0
Affects Version/s: 3.3.1
2.10.1
3.2.2
3.4.0
> 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
> Components: capacity scheduler
> Affects Versions: 3.2.2, 2.10.1, 3.4.0, 3.3.1
> Reporter: Jonathan Hung
> Assignee: Bilwa S T
> Priority: Major
> Fix For: 3.2.2, 2.10.1, 3.4.0, 3.3.1
>
> Attachments: YARN-10260.001.patch
>
>
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
