You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Which service(blob, file, queue, table) does this issue concern?
Blob
Which version of the SDK was used?
12.14.1
Which platform are you using? (ex: .NET Core 2.1)
.NET 6
What problem was encountered?
I have a .NET solution that has implemented a Service scoped to handle all Azure blob operations that the application performs. We see no issues on non-prod environments., but when deployed in prod, we are seeing some random timeouts related to ALL Azure Storage dependencies operations Including:
Its not happening always also with same volumes, so we are not being able to track down the issue, but in essence we are seeing our API request being throttled because of these delays:
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
No
The text was updated successfully, but these errors were encountered:
albertllonch
changed the title
Random timeouts when doing
Random timeouts for Blob Operations
Apr 17, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which service(blob, file, queue, table) does this issue concern?
Blob
Which version of the SDK was used?
12.14.1
Which platform are you using? (ex: .NET Core 2.1)
.NET 6
What problem was encountered?
I have a .NET solution that has implemented a Service scoped to handle all Azure blob operations that the application performs. We see no issues on non-prod environments., but when deployed in prod, we are seeing some random timeouts related to ALL Azure Storage dependencies operations Including:
Its not happening always also with same volumes, so we are not being able to track down the issue, but in essence we are seeing our API request being throttled because of these delays:
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
No
The text was updated successfully, but these errors were encountered: