Skip to main content

Miss-configuration of Azure auto-scaling feature

 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

Popular posts from this blog

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

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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…