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
When we set SSL to TLS 1.2 through the connection string (as stated in this issue) and we upgraded from 5.5.0 to 6.3.4, our Redis clients connections went through the roof.
With the 5.5.0 version, our connections count floats around 600 for our app.
With the 6.3.4 version and the TLS configuration through the connection string, we've seen thousands of connections (as many as our server allowed, 10K).
To Reproduce
Our initial configuration (with the 5.5.0 version and same StackExchange.Redis package) was something like this:
Basically I've removed the invalidate part / reconnect because the multiplex does it automatically. The connection management is like the 5.x version.
Let me know
When we set SSL to TLS 1.2 through the connection string (as stated in this issue) and we upgraded from 5.5.0 to 6.3.4, our Redis clients connections went through the roof.
With the 5.5.0 version, our connections count floats around 600 for our app.
With the 6.3.4 version and the TLS configuration through the connection string, we've seen thousands of connections (as many as our server allowed, 10K).
To Reproduce
Our initial configuration (with the 5.5.0 version and same StackExchange.Redis package) was something like this:
And after the upgrade to 6.3.4 and supports for TLS 1.2, the config looked like that
Expected behavior
No more connections than expected (before upgrading).
Env: Azure Windows App Services:
The text was updated successfully, but these errors were encountered: