-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sporadic loss of connectivity with 2.0.601 #1178
Comments
You may want to tag @mgravell so he's aware of your post. FWIW we're seeing the same issue, also using Azure Redis on 2.0.601. |
Was just coming here to upgrade, guess I'll hold off for now 😁 Is 2.0.593 stable? |
Hi @mgravell , We also run ASP.NET service and use Azure Redis and we are planning to upgrade to 2.0.601 as we are facing lot of issues with older client version (1.2.6) Thanks, |
@mgravell just wanted to let you know that it happened again. Single multiplexer on a VM lost connection (a dozen more on the same VM keep working just fine). Symptoms are the same as described earlier. FWIW first request going through this multiplexer fails with RedisConnectionException"An unknown error occurred when writing the message". Subsequent requests report StackExchange.Redis.RedisConnectionException "No connection is available to service this operation" |
@mgravell i am facing the same issue as well, along with "No connection is available to service this operation" randomly |
Any update on this issue? We're also encountering this errors. |
We are getting ready to deploy an upgrade using the following stack, which includes StackExchange.Redis, and I wondered if anyone had an update on the problem listed in this thread that might concern the reliability of my plan: Microsoft.Web.RedisSessionStateProvider v4.0.1 Should I expect problems with 2.0.601? Thanks in advance. |
2.0.601.3402 has this problem |
2.0.601 has issues** Any suggestion ?
|
This issue is finally tracked down in #1374 - going to close this out to fold the conversations in. Look out for a 2.1.x release soon as we verify and get that behavior change in. |
Hi Marc
We are running ASP.NET services in Azure and use Azure Redis. After upgrading one of our services to 2.0.601 we started observing sporadic loss of connectivity. Our VMs maintain several Redis connections (using several multiplexers). They all share same (default) connection manager.
Occasionally one of multiplexers loses the connection and never recovers. We have to recycle app pool to bring it back to life. When this happens I see few errors in our logs (these are coming from ConnectionMultiplexer events) -
InternalError
followed byConnectionFailed
andConfigurationChanged
. All subsequent Redis requests then fail with "No connection is available to service this operation" error.Here are the events coming from the ConnectionMultiplexer.
Let me know if I can collect more data for you.
Thanks,
Pavel
The text was updated successfully, but these errors were encountered: