Skip to main content

Azure Redis Cache and connection management

These days I encountered an application deployed on Azure that had connectivity issues with Azure Redis Cache.
The application is a web-based application with most of the logic inside Azure Functions. The system it is using Azure Redis Cache for data exchange between the web-application and the functions behind the scene that is crunching the data.
The deployment is stable and working as expected for 5-10 minutes. After that, it is down for the next 20-30 minutes. The cycle repeats over and over again with a generic error on both sides (Azure Web Application and Azure Functions) that indicates that the source of the problem is Azure Redis Cache.

The errors are similar to the one below:
No connection is available to service this operation: RPUSH ST; UnableToConnect on, origin: ResetNonConnected, 

input-buffer: 0, outstanding: 0, last-read: 5s ago, last-write: 5s ago, unanswered-write: 459810s ago, keep-alive: 60s, pending: 0, state: Connecting, last-heartbeat: never, 

last-mbeat: -1s ago, global: 0s ago, mgr: Inactive, err: never; IOCP: (Busy=0,Free=1000,Min=6,Max=1000), WORKER: (Busy=3,Free=8188,Min=6,Max=8191)

The team first reaction was to change the cache tier from C0 to C2 and C3. The problem started not to appear so often, but the price of cache increased drastically for a system that should cost less than 200 per month.
Their mistake was that nobody took a closer look at the error and the Azure Redis Cache metrics available inside Azure Portal. Inside the Portal, it was pretty clear that:
  • The maximum number of connections allowed to the cache was reached
  • In that times, the number of requests that were missed by the cache was 100%
  • Changing the tier of cache instance just increased the number of connections allowed without resolving the main problem
The high number of connections is not normal for an application that has 5 different times of Azure Functions that are configured in such a way to not run in parallel and the maximum number of requests from the Azure Web App to the cache in the same time is up to 4 different connections.

Taking a look at the code we notified that inside Azure Functions a new connection is open each time when data is written to the cache - but without closing the connection. This means that the connection remains open until the timeout occurs for that connection instance.

Cause: Improper use of the API. Each connection instance (ConnectionMultiplexer) needs to be closed manually or use the IDisposable pattern that it is already available. Once the code was updated, there were no issues anymore with it, and we were able to downgrade the cache tier back to the original one.

ConnectionMultiplexer connection = ConnectionMultiplexer.Connect(RedisCacheConnectionString);

IDatabase cacheDb = connection.GetDatabase();
cacheDb.ListRightPush(key, value);



using (ConnectionMultiplexer connection = ConnectionMultiplexer.Connect(RedisCacheConnectionString))
 IDatabase cacheDb = connection.GetDatabase();
 cacheDb.ListRightPush(key, value);


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 …

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.