[
https://issues.apache.org/jira/browse/AURORA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299247#comment-14299247
]
Hudson commented on AURORA-184:
-------------------------------
SUCCESS: Integrated in Aurora #852 (See
[https://builds.apache.org/job/Aurora/852/])
[AURORA-184] Remove hardcoded 'host' and 'rack' limit constraints (zmanji: rev
db6a19994d7fc36b09aa1108d680f3418901d628)
*
src/test/java/org/apache/aurora/scheduler/configuration/ConfigurationManagerTest.java
*
src/main/java/org/apache/aurora/scheduler/configuration/ConfigurationManager.java
> 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)
