Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support service PlacementConstraints #1083

Open
mmdriley opened this issue May 7, 2017 · 0 comments
Open

Support service PlacementConstraints #1083

mmdriley opened this issue May 7, 2017 · 0 comments

Comments

@mmdriley
Copy link

mmdriley commented May 7, 2017

With the 2017-04-28 release of CloudFormation, the AWS::ECS::Service resource now supports the PlacementConstraints and PlacementStrategies properties.

PlacementConstraints seems very useful for the case where an N-task service is scheduled on an N-instance cluster. If nodes cycle, ECS will reschedule tasks to healthy instances, but won't move them back when the instances are replaced. This can leave the majority of tasks on a small number of instances, or all grouped in one AZ, which isn't great for availability. If we set PlacementConstraints to distinctInstance we can prevent two tasks from the same job from starting on the same container instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant