Databases
StackOverflow2013
Postsdbo
POAzure Storage container command running extremely long
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAzure Storage container command running extremely long
    text
    copied!<p>I am working with Azure Storage and having some issues when calling commands on a container. I am running it with a unit test and sometimes when a command is called on a container, it just sits and waits on that command for almost 5 mins. And if I wait long enough, it will continue and succeed. When running this, the container actually does exist so it's not having to create the container at all.</p> <p>Has anyone else run into this problem? I tried setting a <code>ServerTimeout</code> on the <code>BlobRequestOptions</code> but it had no affect.</p> <p>Here is a sample of what my code is doing:</p> <pre><code>var blobClient = _storageAccount.CreateCloudBlobClient(); var container = blobClient.GetContainerReference(containerName); var options = new BlobRequestOptions() { ServerTimeout = TimeSpan.FromSeconds(10) }; if (!container.Exists(options)) //&lt;&lt;&lt;&lt;this is where it hangs { container.Create(); } </code></pre> <p>I have also tried it with <code>CreateIfNotExists()</code>:</p> <pre><code>var blobClient = _storageAccount.CreateCloudBlobClient(); var container = blobClient.GetContainerReference(containerName); container.CreateIfNotExists(); //&lt;&lt;&lt;this is where it hangs </code></pre> <p>It also hangs if I just try to list the blobs</p> <pre><code>var blobClient = _storageAccount.CreateCloudBlobClient(); var container = blobClient.GetContainerReference(containerName); container.ListBlobs(); //&lt;&lt;&lt;&lt;this is where it hangs </code></pre> <p>It doesn't happen for every container but when it does happen for one, it seems to be the same one. I have checked and the container does exist.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload