Skip to main content

Azure Load Balancer and Sticky Connection (Source IP Affinity)

In this post we will talk about Azure Load Balancer and how we can have stick connection to our Azure Resources when we have multiple instances.

When we are using Azure VMs, Web Roles or Worker Roles and having multiple instances of the same type, all our requests will fly through a Azure Load Balancer. By default, Azure Load Balancer is not offering sticky sessions based on Source IP and Destination IP (see the last part of blog post).
This means that multiple requests that are coming from the same client are not guaranteed to end up to the same instance when port is changing. Based on different counters, like CPU level for example, Azure Load Balancer can decide to redirect a request to another instance.
There are cases when we need sticky connection and all the requests to end up to the same instance on Azure side. A good example is a relay server, where ports are changing for each request. In this case we need to be sure that all requests from the same source end up on the same instance.
Another example is for cases when we have a web application and we want all the requests from the same client to end up on the same instance, even when the requests are made using different ports (80, 8080, 443, ...)

In the above example we can observe that two different request from the same client, where the source port is different can end up on different instances.

Azure Solution
Azure Load Balancer supports this features, offering us the possibility to have sticky connections. This custom configuration of Azure Load Balancer is called Source IP. It allow us to bind a client to a specific instance from Azure. In this case, when we multiple instance in the backend, we will know that requests from the same client will end up on the same instance.

The bind between client and instance is formed by two types of tuples:
  • Client IP, Destination IP
  • Client IP, Destination IP, Protocol
Type of instances supported
In this moment there 3 types of instances that are support
  • Web Roles
  • Worker Roles
  • Virtual Machines 
, and load balancer endpoints.

How to configure
The configuration is very similar for all types of instances. We need to set the load balancer distribution to 'sourceIP'. 
Web/Worker Roles
This can be done from the .csdef file, in the moment when we configure the input endpoint. See below example:
<WorkerRole name="foo" vmsize="small" enableNativeCodeExecution="false">
    <InputEndpoint ... loadBalancerDistribution="sourceIP" />
Load Balancer Endpoint
This can be done using Power Shell, by setting the LoadBalancerDistribution attribute to 'sourceIP'

What we should be aware when using default Azure Load Balancer configuration
By default, Azure Load Balancer is using a tuple formed from 5 elements

  • (source IP, source port, destination IP, destination port, protocol type)
This means that we have a stick connection already, but the source port and destination port are used also to identify the instance. If we have multiple requests, with different port source or destination ports and we want to keep them on the same instance, that we should use Source IP Affinity.

In conclusion we should keep in mind what kind of sticky connection we need and what part of a request will define our sticky connection (IP, ports, protocol).


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 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 …

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.

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…