[AURORA-184] Implicit scheduling constraints should be removed

• Type: Story
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.8.0
• Component/s: Scheduler
• Assignee: Florian Pfeiffer
• Reporter: Kevin Sweeney
• Created: 04/Feb/14 01:54
• Updated: 04/May/15 14:32
• Resolved: 30/Jan/15 19:26

Description

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.

Issue Links

• duplicates: AURORA-174 injected scheduler constraints should be configurable
• is duplicated by: AURORA-212 Modify default rack limit to be something other than 1 (perhaps N/10)
• is duplicated by: AURORA-662 Remove Rack Limit Default
• relates to: AURORA-174 injected scheduler constraints should be configurable