hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Templeton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7107) add ability in Fair Scheduler to configure whether disable a queue
Date Mon, 28 Aug 2017 17:23:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144085#comment-16144085
] 

Daniel Templeton commented on YARN-7107:
----------------------------------------

+1 on the need to disable queues.  I was just saying last week that we need the feature. 
It sounds to me, though, that what you're trying to do is implement an override queue, which
is something we could support more explicitly.  We could add a special "override" queue weight
that makes all other queues effectively have 0 weight if the override queue is active.  Just
a thought.

> add ability in Fair Scheduler to configure whether disable a queue
> ------------------------------------------------------------------
>
>                 Key: YARN-7107
>                 URL: https://issues.apache.org/jira/browse/YARN-7107
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: YunFan Zhou
>            Assignee: YunFan Zhou
>              Labels: fairscheduler
>
> In a production environment, emergency situations (such as the need to calculate the
important reports) as soon as possible we need to disable all other queues, only allows the
*RM* 's resources assigned to emergency queue and other queue only at the end of the urgent
tasks before allowing them to be scheduled properly.
> At present, our approach is to write a script, in the case of an emergency manual changes
all other queues' *minResources *and *maxResources * to *0mb, 0vcores* and then rebase it.This
is very troublesome and easy to make mistakes.
> So we need to add a configuration in the *FairScheduler* configuration to indicate whether
the queue is disabled, and if it is disabled, then *RM *will not allocate resources to the
queue.
> * The child queue will integrate this property of the parent queue.
> * If the child queue is configured with this property, the value of the child queue configuration
overrides the attributes of the parent queue.
> * The default value of the root queue is *enabled*.
> This will satisfy our needs, and I think other users will encounter such a scenario.I
think this is very applicable to everyone.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message