-
Notifications
You must be signed in to change notification settings - Fork 1.5k
No connection is available to service this operation #1387
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
Comments
There is no load on the service |
2.0.519 |
@zhanghaiboshiwo are you using a Redis cache cluster like Azure Redis? |
No,It is simple |
only one |
@zhanghaiboshiwo might be related to #1374 but not quite sure. Can you see if this reproes in 2.1.0? It was released yesterday. |
I just stumbled upon this when trying to run issue : dotnet/aspnetcore#20040 |
@tebeco Are you saying it's reproduce-able in some config in 2.1.0? If so, I'm very, very curious! |
the repro for me is
|
here is what i see in the
and
|
i do confirm that it does reproduce and VS it telling me that |
@tebeco This didn't click back then but was an underlying issue resolved in #1947. Look out for the v2.5 release to have "make sure subscriber is connected before Connect(Async) comes back", "heartbeat keeps pub/sub connection alive properly", "better subscription restore handling on reconnect", and "by-default backlog to handle disconnects more gracefully". In total, this should resolve a lot of problems - see the #1947 PR for more details! |
No connection is available to service this operation: SETEX string:testkey; IOCP: (Busy=1,Free=999,Min=2,Max=1000), WORKER: (Busy=0,Free=32767,Min=2,Max=32767), Local-CPU: n/a
The text was updated successfully, but these errors were encountered: