[
https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740597#comment-13740597
]
Vinod Kumar Vavilapalli commented on YARN-1004:
-----------------------------------------------
Like I mentioned, Fifo and CS both already depend on it and have the same
meaning. Only FairScheduler diverges in meaning. Adding a new tag in the name
is akin to adding more description. Let's not break the minimum config now,
particularly given MAPREDUCE-5311 's dependency on a min-allocation config.
> yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed
> with the scheduler type
> --------------------------------------------------------------------------------------------------
>
> 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
