You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/08/01 08:41:52 UTC

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

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

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

Uploaded a patch that adds "fair", "capacity", and "fifo" to the minimum and increment configs.  The patch turned out to require quite a few changes.  I wasn't sure how to deal with the slots-millis job counter - it seems like it doesn't make sense in the context of MR2 - so I removed it.  If this would delay the release I'm not sure it's worth it.

[~tucu], you worked on the per-scheduler separation of these configs.  Any thoughts?
                
> 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
>         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