You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bilwa S T (Jira)" <ji...@apache.org> on 2020/05/07 15:00:00 UTC
[jira] [Comment Edited] (YARN-10260) Allow transitioning queue from
DRAINING to RUNNING state
[ https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101746#comment-17101746 ]
Bilwa S T edited comment on YARN-10260 at 5/7/20, 2:59 PM:
-----------------------------------------------------------
[~jhung] Thanks for raising this issue
Instead of throwing exception when configstate is RUNNING and currentState is DRAINING, we can activateQueue() . Thoughts?
was (Author: bilwast):
Hi [~jhung]
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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org