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
Rack instance count must be >= 3 #1395
Conversation
Current coverage is 29.08% (diff: 50.00%)@@ master #1395 diff @@
==========================================
Files 137 137
Lines 12900 12900
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
Hits 3752 3752
Misses 8750 8750
Partials 398 398
|
@MiguelMoll the trello board is private - so not sure why this was enforced, we have one client where three instances is a bit overkill for their application. We'll have to increase it, but wondering why this was needed? |
Sure. Since Rack runs two copies of the Rack API process for optimal uptime, if a Rack doesn't have at least three instances updates can't roll out and your CloudFormation stack will get wedged. When Cloudformation tries to rollback the update, the limit of two instances prevents the rollback from succeeding. We've seen a few users getting stuck because of this scenario recently. |
@MiguelMoll fair enough, could the API not set with a minimum of 1 process running? and an optimal of 2 |
That is an option we considered but didn't go down that route just yet. Could be an option in the future. |
Enforce minimum of 3 Rack instances instead of 2.
A Rack with an instance count <= 2 will have to bump the instance count to at least 3 before updating.