[
https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867262#comment-13867262
]
Sandy Ryza commented on YARN-1567:
----------------------------------
bq. Didn't say that we should stop this. If we are doing this for FS, I was
mentioning that we should do it for CS too assuming the validity of the
use-case.
Ah, sorry, misunderstood. In that case, I totally agree we should add this in
a way that keeps the semantics consistent across the schedulers.
I just read up on the meaning of QueueState in the Capacity Scheduler. Looks
like we should be able to add the same to the Fair Scheduler.
I think queues should need to be empty, not necessarily stopped, to do a
leaf<->parent change. Like the leaf<->parent change, changing a queue from
empty to stopped occurs on scheduler configuration reload. I see no reason that
we should require two reloads to turn an empty leaf queue into a parent. We
should of course ensure that we are synchronizing properly so that an app does
not end up getting to submitted to the queue that is now a parent.
> 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)
