[
https://issues.apache.org/jira/browse/YARN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320592#comment-14320592
]
Vinod Kumar Vavilapalli commented on YARN-2986:
-----------------------------------------------
Tx for the comments.
What is the difference between scheduler-custom-configuration and
global-options? I was trying to put a structure around the global options for
less confusion, but I am not too opinionated either ways.
bq. I think we shouldn't mix element/attribute in config file
Yes, I was trying to use elements everywhere, except for custom scheduler
options. We can change that though.
bq. Beyond above comments, what's the plan to support the two different
configurations?
We should support the old one also. At any point of time, we can chose to
support (a) both old and new configuration with old configurations taking
precedence or (b) only support new configuration style if configured, and use
the old configurations otherwise. I think (b) is enough for us.
> 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: Vinod Kumar Vavilapalli
>
> 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)
