aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AURORA-184) Implicit scheduling constraints should be configurable
Date Wed, 19 Feb 2014 21:24:20 GMT

     [ https://issues.apache.org/jira/browse/AURORA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bill Farner resolved AURORA-184.
--------------------------------

    Resolution: Duplicate

> Implicit scheduling constraints should be configurable
> ------------------------------------------------------
>
>                 Key: AURORA-184
>                 URL: https://issues.apache.org/jira/browse/AURORA-184
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Kevin Sweeney
>
> Right now the scheduler hardcodes "host" and "rack" limit constraints into submitted
jobs. These require slave attributes to be set on the slave command-line, which means deploying
aurora on a running mesos cluster needs a hard slave restart (changing slave attributes invalidates
recovery metadata, meaning underlying tasks must be killed). In addition, "host" and "rack"
might not accurately capture failure domains in other mesos deployments.
> Make this constraint-set configurable at deploy-time, defaulting to empty.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message