[
https://issues.apache.org/jira/browse/YARN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333728#comment-14333728
]
Wangda Tan commented on YARN-2986:
----------------------------------
Hi [~sunilg],
Thanks for sharing your thoughts :).
bq. Do you mean that, non repeating items are kept outside loop of queues and
changing items are kept inside each queue?
No, what I meant is, if a field *need* to be set in queue level,
policy-properties should be a part of queue, and also global is some fields
need to be "global".
For your 2nd point, providing a way to make policy-properties linkable.
However, I think for most of the fields, like capacity, label settings, etc.
should be different for different queues, adding links might make people get
confused. And queues have to overwrite some fields to make their own.
Alternatively, I think we can use inherit to make configuration easier, for
example, a parent queue's accessible-node-labels will be inherited by its
children if its children don't overwrite.
Thoughts?
> (Umbrella) Support hierarchical and unified scheduler configuration
> -------------------------------------------------------------------
>
> Key: YARN-2986
> URL: https://issues.apache.org/jira/browse/YARN-2986
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Wangda Tan
> Attachments: YARN-2986.1.patch
>
>
> Today's scheduler configuration is fragmented and non-intuitive, and needs to
> be improved. Details in comments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
