You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2014/09/02 18:15:20 UTC

[jira] [Commented] (AURORA-662) Improve Rack Limit Default

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

Bill Farner commented on AURORA-662:
------------------------------------

There's precedent for defaults in other configuration fields, i could see default=0 being reasonable.

> Improve Rack Limit Default
> --------------------------
>
>                 Key: AURORA-662
>                 URL: https://issues.apache.org/jira/browse/AURORA-662
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Zameer Manji
>            Assignee: Zameer Manji
>
> If a rack limit for a job is unspecified, the scheduler places a default of 1. This default is naive and can make large jobs impossible to schedule.
> We should replace this default with something that is little bit smarter. It should factor in the size of the job and potentially the number of racks available.
> The code that creates the default is [here|https://github.com/apache/incubator-aurora/blob/900a2b299347c71f7c7601a3a3d0a3f0f0afbcb7/src/main/java/org/apache/aurora/scheduler/configuration/ConfigurationManager.java#L142-L153].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)