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: https://github.com/WindowsAzure/azure-storage-net/tree/master/Lib/Common/RetryPolicies.
The retry policy is set through Options of different requests or through the client itself.
CloudBlobClient bc = sa.CreateCloudBlobClient(...)
bc.RetryPolicy = new LiniarRetry();
...
OR
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.

Comments

Popular posts from this blog

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

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP