Skip to main content

Miss-configuration of Azure auto-scaling feature

By

 Let's talk about Azure autoscaling feature. I found often people that are configure autoscaling without understanding what each item from the configuration panel represents. 

THE STORY


One of my friends called me a few days ago telling me that the scaling configuration of the App Service that he manages does not work as expected and there might be a bug. It is not common to find such issues on autoscaling capabilities, because of this I suspected from start a miss-configuration.

The reported problem was related to how fast the no. of instances are growing. After reviewing the configuration I notified that the cooldown time period was configured wrong.

AUTOSCALING INSIGHTS

Let's start with an example. We have autoscaling configured for a web app that is using Standard App Service Plan. The scaleout is configured with the following configuration:

  1. When the average CPU level is greater than 70, for more than 40 minutes, increase count with 3
  2. When the average CPU level is greater than 50, for more than 120 minutes, increase count with 2
  3. When the average CPU level is less than 20, for more than 60 minutes, decrease count with 1
The problem with this configuration was that after first scaling, every 20 minutes the rules were run again, and a scaling action was taken. Because of this, the no.of instances was all the time changing.

The misconfiguration was at the cooldown value, which was set to 20 minutes and was triggering the check fo the rules every 20 minutes. The wrong assumption was that after the cooldown period, Azure will wait for another 40 minutes to check the rule no. 1, 120 minutes to check the rule no. 2 and 60 minutes for rule no 3. 
The way how cooldown is working is that after the given interval (in our case 20 minutes) the rules are checked one more time. The solution was simple, just changing the value of cooldown from 20 to 60 minutes. 

Cooldown - The amount of time to wait before the rule is applied again so that the autoscale actions have time to take effect.

TAKE AWAY
The rules that are configured to scale out or scale in are checked each time after the cooldown period passes away. It is important to identify a time interval for the cooldown period that suits your needs, especially when the time interval for scale-out and scale in are longer. 









Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more