[BUG][Storage] server return 404 also retry

Describe the bug blob client call GetPropertiesAsync will retry even though server return 404? We have a case, get a blob path return 404, but it takes too long for me. In Application insight, we can see it will retry 6 times. but we don’t config the client retry policy.

Expected behavior

don’t retry.

Actual behavior (include Exception or Stack Trace)

retry 6 times

To Reproduce Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

Environment:

• Azure.Storage.Blobs 12.4.4
• Win 10 and netstandard2.0
• Visual Studio 16.8

[yunair]

I have reproduce this problem, just set GeoRedundantSecondaryUri same as serviceUrl

[older]

I have reproduce this problem, just set GeoRedundantSecondaryUri same as serviceUrl

Thank you @yunair your comment helped me a lot!

It is really weird that this bug is still not fixed even in the latest version of SDK (I’m using Azure.Storage.Blobs 12.13.1 right now). I wasted couple of days trying to understand what I’m doing wrong. @amnguye you still cannot reproduce it? Here’s how to create client so you can see it. Note that the same value is used as bot primary and secondary URI.

var containerClient = new BlobContainerClient(containerUri, new BlobClientOptions
                {
                    GeoRedundantSecondaryUri = containerUri,
                });

Then use containerClient on any non-existing blob name, and you can observe that it will run retries on http status 404 from the storage API.