Azure Storage container team takes a very long time

Question

I work with Azure Storage and have some problems when invoking commands in the container. I run it with the unit test, and sometimes when the command is called in the container, it just sits and waits for this command for almost 5 minutes. And if I wait long enough, it will continue and succeed. When this container starts, it actually exists, so it does not need to create a container at all.

Anyone else run into this issue? I tried setting ServerTimeout to BlobRequestOptions , but that did not affect.

Here is an example of what my code does:

 var blobClient = _storageAccount.CreateCloudBlobClient(); var container = blobClient.GetContainerReference(containerName); var options = new BlobRequestOptions() { ServerTimeout = TimeSpan.FromSeconds(10) }; if (!container.Exists(options)) //<<<<this is where it hangs { container.Create(); } 

I also tried it with CreateIfNotExists() :

 var blobClient = _storageAccount.CreateCloudBlobClient(); var container = blobClient.GetContainerReference(containerName); container.CreateIfNotExists(); //<<<this is where it hangs 

It also freezes if I just try to list blobs

 var blobClient = _storageAccount.CreateCloudBlobClient(); var container = blobClient.GetContainerReference(containerName); container.ListBlobs(); //<<<<this is where it hangs 

This does not happen for every container, but when it happens for one, it seems to be the same. I checked and the container exists.

Answer 1

I reported a very similar situation: Checking for an element in an Azure blob container takes forever (SDK 2.0) . Have not found an answer yet.

Answer 2

Can you connect Fiddler to the setup and see if any relevant information comes out? (see http://sepialabs.com/blog/2012/02/17/profiling-azure-storage-with-fiddler/ for setting this parameter)

If not, I would advise you to seek support.