[
https://issues.apache.org/jira/browse/AURORA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zameer Manji updated AURORA-184:
--------------------------------
Summary: Implicit scheduling constraints should be removed (was: Implicit
scheduling constraints should be configurable)
> 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)
