-
Notifications
You must be signed in to change notification settings - Fork 4
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
"Service... did not stabilize" error when updating the CloudFormation stack #175
Comments
This changeset execution is currently consuming all but 747 MB of memory on the EC2 instances: And it's taking an awfully long time to resolve either way... And the |
ConclusionWhat caused this to fail? Who can know for sure? The fact that one of our Tasks - when spun in two instances, without the "spread" settings from PR 38 already in place - could still potentially swamp the remaining memory on an EC2 host, is a very likely candidate. We *shouldn't see this any longer, so long as the cluster (a) keeps the "spread" settings, and (b) never tries to launch a Service that could consume the remaining memory on the EC2 host. |
Attempted to update the CF stack last night with the changes due to PR 38:
Observed conditions
Theory on the failure
Evidence for this theory
The text was updated successfully, but these errors were encountered: