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

Provide 'cooldown' period configuration to mitigate aggressive scale-up #284

Open
hungwunfai opened this issue Jan 21, 2016 · 1 comment

Comments

@hungwunfai
Copy link

The throttle triggered scale-up is often too aggressive, due to a lag between capacity being set and actual throttle going away. It would be extremely helpful to have a cooldown period configuration that defines how long to wait after a scale-up or scale-down action before another one.

@ninjada
Copy link

ninjada commented May 20, 2016

+1, especially on downscales, with the 4x per day limit.

Any cost gains im making can be wiped out pretty quickly.

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

2 participants