[
https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866877#comment-13866877
]
Sandy Ryza commented on YARN-1567:
----------------------------------
The Fair Scheduler does not have a notion of stopped queues.
While there is a lot in queue definitions and behavior that we can consolidate,
I don't think that we should use conciliation as a sole basis for stopping new
features. Is there a reason that the way the Capacity Scheduler works is
fundamentally incompatible with changing queues from leaf to parent? Queues
have a lot in common once they exist, but the way queues are configured,
loaded, and managed may be different to the point of irreconcilable between the
Capacity Scheduler and Fair Scheduler.
Also, I realized I left out the motivation for this. The use case behind this
is the following:
Sally gets a leaf queue created for her division, SallysQueue. As usage starts
to ramp up, her teams start complaining that their workloads are stepping on
each other's toes. She would like to be able to divide up the resources
allocated to her division between her teams without restarting the RM.
> In Fair Scheduler, allow empty queues to change between leaf and parent on
> allocation file reload
> -------------------------------------------------------------------------------------------------
>
> Key: YARN-1567
> URL: https://issues.apache.org/jira/browse/YARN-1567
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 2.2.0
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-1567-1.patch, YARN-1567.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
