SQL Connection hang issue with .Net 5 and Microsoft.Extensions.Caching.SqlServer 5.0.1

[msmaverick2018]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I am using Microsoft.Extensions.Caching.SqlServer 5.0.1 in an asp net core application running in docker container using base image "aspnet:5.0-buster-slim". The application started hanging after deploying in one of our environments with CPU utilization shooting high, ultimately getting throttled by the limits. It took a long while to understand what was going on but finally we realized it was an issue with TLS 1.2, the sql server in the environment was not patched to handle it.
The issue is described here and the fix was done here and has been fixed in version 2.0 of Microsoft.Data.SqlClient as mentioned in release notes. It will be great if sql client reference is updated atleast to version 2.0 so that we do not run into this issue. Right now it is using version 1.0.

Expected Behavior

• CPU Utilization should not shoot up in case of TLS errors
• Should respect default connection timeout for SQL Connection or any overriding value.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[adityamandaleeka]

We should update this in 7. https://github.com/dotnet/aspnetcore/blob/main/eng/Versions.props#L279

As a workaround, it might be possible to update the dependency directly in your app.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.