-
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
StackExchange.Redis.RedisConnectionException: No connection is available to service this operation: PUBLISH content #1147
Comments
The first exception that happens (before it collapses) does seem to be a TimeoutException. Here's an example:
Both |
We rolled back to I would love to figure out what's going on though as I would like to move to v2 when it's ready. |
We are observing similar problem. Our application is running on .NET Core 2.2. It is fully asynchronous and basically this happens under load, when there is large amount of async tasks being queued by the various logic on the application. Some of these tasks are also performing Redis read/writes. Reading the documentation of the Redis client I was under the impression that it had been rewritten to utilize its own pool of threads for handling the Redis operations. May be the threads on this pool are starving for CPU due to the overall load on the rest of the application or are somehow blocked. |
Same issue here as well with vs .601. Any resolution in sight, or do i need to roll back? |
We upgrade to the v2 version recently and since then have started seeing these exceptions. When this happens, we have to restart the service instance in order for it to reconnect.
However, it seems that about an hour after the restart occurs, we get the same issue show up.
We're rolling back to the v1 library to mitigate the issue, but would like to find out what could be happening.
We're using the Azure Redis Cache for Pub/Sub only. The redis instance is hosted in West US 2 and used by services running in West US 2 and East US. In our case, only Easst US is running into these issues.
Here is the full exception information:
StackExchange.Redis.RedisConnectionException: No connection is available to service this operation: PUBLISH content; An existing connection was forcibly closed by the remote host; IOCP: (Busy=1,Free=999,Min=4,Max=1000), WORKER: (Busy=0,Free=32767,Min=4,Max=32767), Local-CPU: n/a ---> StackExchange.Redis.RedisConnectionException: SocketFailure on intentcontent-prod-westus2.redis.cache.windows.net:6380/Interactive, Flushing/Faulted, last: PUBLISH, origin: ReadFromPipe, outstanding: 984, last-read: 18s ago, last-write: 12s ago, keep-alive: 60s, state: ConnectedEstablished, mgr: 7 of 10 available, in: 0, last-heartbeat: 0s ago, last-mbeat: 0s ago, global: 0s ago, v: 2.0.600.65315 ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Anyone know if the info in the exception message is helpful? And what we can do to investigate further?
The text was updated successfully, but these errors were encountered: