Skip to main content

Windows Azure Storage and Read-Access Geo Redundant Feature (Part 2)

Part 1
In the last post we describe the new feature of Windows Azure Storage that give us the possibility to not only replicate the storage content to another datacenter, but also access in in read-only mode when the primary storage is down - Read Access Geo Redundant Storage (RA-GRS)
In this post we’ll talk about some things that we should be aware when we are staring to use RA-GRS.

Retry Policy
First thing that we need to be aware is the retry policy. With geo redundant feature we need another retry policy that can automatically fall back to the second account when the first down cannot be accessed.
For this purpose a new interface was created called “IExtendedRetryPolicy” was created. This new interface comes with a method called “Evaluate” that detect if the operation should be retried or not. Because we have two storage accounts that needs to be checked there is a small change in behavior. We need a mechanism to switch the two accounts and also to take into the consideration the time interval.
For this behavior we have already an implementation “ExponentialRetry” and “LiniarRetry” that take into account all this things. If you have time you can look over the implementation here:
The retry policy is set through Options of different requests or through the client itself.
CloudBlobClient bc = sa.CreateCloudBlobClient(...)
bc.RetryPolicy = new LiniarRetry();
BlobRequestOptions bro = new BlobRequestOptions()
  RetryPolicy = new LiniarRetry(),
  ServerTimeout TimeSpan.FromMinutes(1),  
CloudBlockBlob blob = container.GetBlockBlobReferecen("FooName");
blob.DownloadFile( fileName, FileMode.OpenOrCreate, null, bro );
TableRequestOptions tro = new TableRequestOptions()
  RetryPolicy = new LiniarRetry(),
  ServerTimeout TimeSpan.FromMinutes(1),  
QueueRequestOptions tro = new QueueRequestOptions()
  RetryPolicy = new LiniarRetry(),
  ServerTimeout TimeSpan.FromMinutes(1),  

Location Mode
In the last post we talk about this property, but when we should set this value? This value should be set at the request option object. There we have a property called LocationMode that will allow to do this.
CloudBlobClient bc = sa.CreateCloudBlobClient(...);
bc.LocationMode = LocationMode.SecondaryOnly;
In this example if the primary account is down (404) or we have a timeout expectation, that a fallback to the second account is made.

In this post we saw how we can change the retry policy when we use the Read Access Geo Redundant Storage.


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.