[
https://issues.apache.org/jira/browse/YARN-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151841#comment-16151841
]
YunFan Zhou commented on YARN-7107:
-----------------------------------
Thank [~templedf] for your review, I benefited a lot from your advice.
Your solution is so perfect for:
* Do not allocate resources to disabled queue.
* The disabled status of the queue can be viewed with the CLI way.
Basically, can meet our requirements.
But the current solution is more difficult to solve the problem we face in our
production environment. Because in our production, we have hundreds of queue,
but in the emergency case, we only want to make sure a few queues (because of
this few queues be used to produce important reports) can be normally assigned
resources.
If we use the way you suggest, we have to set the remaining hundreds of queues
to be disabled.
This makes the operation very cumbersome.
We need a better way to solve this problem， what do you think?
> 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
> Attachments: YARN-7107.001.preview.patch
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
