Auto-Scale explanation of Cool-Down period
We need better explanation of auto-scaling rules. Even after reading MSDN documentation, it is unclear.
Does a Cool-Down period for scale-down interfere with a scale-up operation? For instance, we have a polling period of 5 minutes for scale up, and 120 minutes Cool-Down for scale down. If however, during the 120 minute Cool-Down period of scale-down no further scale-up operation can take place, this would be awful. Sadly, no information is available.
Or what happens if a CPU-Metric-Rule says scale down: but a scale-up Memory-Metric is still firing?
Lastly, we need infos as to whether rule-sets (more than one) are linked with AND or with OR conditions?
Please provide detailed documentation and in-app infos.
We’ll take a look at this
Jyoti Prakash commented
The cool down period which means that if a scale down/up operation has happened, even if the rule is true (example - CPU remains high), the next scale up event will not trigger. Cool down is 5 min which means that if a scale down/up operation has happened, for the next 5 minutes, even if the rule is true, it will not be triggered due to cool down period.
Gopi K commented
yes , looking for Cooldown period settings which instance will be removed first ..
Jonas Samuelsson commented
I would also like some clarification here, does the cooldown period apply to the rule where it's defined or all rules?
2 years have passed -- it is still "under review"? Can we please get an answer to this simple question? Is there any way that Microsoft can update documentation to more clearly explain how the cooldown period works when multiple scaling rules are applied?
Nizar Abdat commented
Yes! We are also facing the same problem.
Jonas Hansen commented
Agreed! Any updates to this one?