[
https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867219#comment-13867219
]
Vinod Kumar Vavilapalli commented on YARN-1567:
-----------------------------------------------
bq. I don't think that we should use conciliation as a sole basis for stopping
new features
I get the use case. 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.
bq. The Fair Scheduler does not have a notion of stopped queues.
bq. 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.
We've done the reconciliation in Hadoop-1. Though not in the 1.x line. It
happened in 0.21/0.22. So I can see how it can be done in Hadoop-2 also.
> 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)
