aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AURORA-184) Implicit scheduling constraints should be configurable
Date Tue, 07 Oct 2014 01:06:34 GMT

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

Zameer Manji reopened AURORA-184:
---------------------------------
      Assignee: Zameer Manji

I don't think this is a dupe of AURORA-174. This ticket aims to remove 'host' and 'rack' injections.
AURORA-174 is about making auto injections configurable.

> 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
>            Assignee: Zameer Manji
>             Fix For: 0.5.0
>
>
> 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.3.4#6332)

Mime
View raw message