You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Zameer Manji (JIRA)" <ji...@apache.org> on 2015/01/30 20:27:35 UTC
[jira] [Resolved] (AURORA-184) Implicit scheduling constraints
should be removed
[ https://issues.apache.org/jira/browse/AURORA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zameer Manji resolved AURORA-184.
---------------------------------
Resolution: Fixed
> Implicit scheduling constraints should be removed
> -------------------------------------------------
>
> Key: AURORA-184
> URL: https://issues.apache.org/jira/browse/AURORA-184
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Kevin Sweeney
> Assignee: Florian Pfeiffer
>
> 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)