We are continuously addressing and improving the SDK. Please describe your issue along with the following information:
SDK version
1.0.8
Issue reproduce steps
Create one CloudTableClient
in a loop with the same table name:
Call tableClient.GetTableReference(tableName);
call table.CreateIfExistsAsync()
call Table.ExecuteAsync() with a query
We do this in a app 4-6 times per page load and we're noticing a lot of HttpClients left behind. In our production Azure App Service, we're running out of sockets within 3-4 hrs and have to restart the app service
Whether the issue is consistent or sporadic
Consistent
Environment Summary
Windows 10, .NET Core 3.1 LTS
** Any other context, such as stack trace or log.
I can provide a stack dump internally if you email me @ my microsoft.com address.
I am experiencing the same issue, because of this, we have socket exhaustion.
Netstat shows hundreds of established connections to the Azure cloud storage IP.
SDK version 1.0.8 Issue reproduce steps Create one CloudTableClient
in a loop with the same table name: Call tableClient.GetTableReference(tableName); call table.CreateIfExistsAsync() call Table.ExecuteAsync() with a query
We do this in a app 4-6 times per page load and we're noticing a lot of HttpClients left behind. In our production Azure App Service, we're running out of sockets within 3-4 hrs and have to restart the app service Whether the issue is consistent or sporadic Consistent Environment Summary Windows 10, .NET Core 3.1 LTS ** Any other context, such as stack trace or log.
I can provide a stack dump internally if you email me @ my microsoft.com address.