[ 
https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725476#comment-13725476
 ] 

Sandy Ryza commented on YARN-1004:
----------------------------------

[~hitesh], maximum-allocation is just for consistency.  My thought is that it 
should be scheduler-specific because it's up to the scheduler to honor the 
config.  Someone could write a new scheduler and not handle it.  We have other 
configs, such as node-locality-threshold, that function the same for the Fair 
and Capacity schedulers as well.

[~bikassaha], I think this is important in that in my experience having these 
properties that function differently for different schedulers has made 
explaining resource configuration really difficult.  I didn't want to delay the 
release, but I'll upload a patch today without deprecations and we can decide 
where to go from there.
                
> 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
>
> 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

Reply via email to