[
https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727921#comment-13727921
]
Vinod Kumar Vavilapalli commented on YARN-1004:
-----------------------------------------------
bq. Isn't it simpler for FS to ignore the existing configs?
Agreed, +1. Originally the max and min configs WERE scheduler specific. Then we
realized that the App writers need to know about it irrespective of security
and moved it out. Even now, CS and fifoScheduler will have the same semantics
for this config. We should leave these around and deprecate it if and when CS
and Fifo also diverge from this meaning.
> yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler
> ----------------------------------------------------------------------------
>
> Key: YARN-1004
> URL: https://issues.apache.org/jira/browse/YARN-1004
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 2.1.0-beta
> Reporter: Sandy Ryza
> Priority: Blocker
> Attachments: YARN-1004.patch
>
>
> As yarn.scheduler.minimum-allocation-mb is now a scheduler-specific
> configuration, and functions differently for the Fair and Capacity
> schedulers, it would be less confusing for the config names to include the
> scheduler names, i.e. yarn.scheduler.fair.minimum-allocation-mb,
> yarn.scheduler.capacity.minimum-allocation-mb, and
> yarn.scheduler.fifo.minimum-allocation-mb.
> The same goes for yarn.scheduler.increment-allocation-mb, which only exists
> for the Fair Scheduler, and yarn.scheduler.maximum-allocation-mb, for
> consistency.
> If we wish to preserve backwards compatibility, we can deprecate the old
> configs to the new ones.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
