[
https://issues.apache.org/jira/browse/YARN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337372#comment-14337372
]
Wangda Tan commented on YARN-2986:
----------------------------------
Hi [~jianhe],
I think it should only take effect when user puts it to correct place, we can
either ignore it or throw exception when user puts it to a incorrect tag.
Adding "policy-properties" is a double-edged sword, as you said, user has to
learn which configuration should be "policy-properties". But in the other hand,
if we support different policy for different queues in the future (e.g. some
queues are fair-based scheduling, some queues are fifo-based scheduling, some
queues are "priority" based scheduling). Admin can get clear understanding,
when policy need changed/updated, which fields need to be
added/removed/updated. I more prefer adding the "policy-properties".
Thanks,
> (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)
