A web application runs on an Azure Virtual Machine Scale Set named `ecom-vmss`. You configure autoscale rules where scale-out occurs when CPU usage exceeds and scale-in occurs when CPU usage falls below . During periods of normal operation, the scale set repeatedly adds and removes instances in rapid succession. You need to resolve this issue. What should you do?
- Decrease the scale-in metric threshold to a lower value, such as .Cevap
- BChange the upgrade policy of the scale set from Automatic to Manual.
- CChange the orchestration mode of the scale set to Flexible.
- DConfigure the scale-in policy to DeleteNewest.
Cevap
Decrease the scale-in metric threshold to a lower value, such as .
Decreasing the scale-in metric threshold (for example, to ) creates a wider gap between the scale-out threshold () and the scale-in threshold. This buffer prevents the scale set from immediately deleting newly created instances when the average CPU load decreases post-scaling, thereby stopping the thrashing cycle.
Adım Adım Çözüm
Anahtar Kavram
Autoscale thresholds and thrashing prevention
Tahmini Süre:1m 0s