StackExchange / StackExchange/StackExchange.Redis

StackExchange.Redis.RedisConnectionException: ......... ConnectTimeout, command=GET, timeout: 2000, inst: 0, qu: 1, qs: 0, aw: False, bw: SpinningDown, rs: NotStarted, ws: Idle, in: 0, last-in: 0, cur-in: 0, sync-ops: 43, async-ops: 2

Open
#2,868 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
6.2k
Forks
1.6k
Avg merge
1d 15h
Merged PRs (30d)
43

Description

We are in process of migrating from .NET framework to.NET 8.
Our services are on azure Kubernetes environment.
From .NET framework services, we could connect to Redis.
But from .NET 8 we are receiving below exception from Redis.
Appreciate your help on suggesting any fixes for these Redis connectivity issues.

StackExchange.Redis.RedisConnectionException: The message timed out in the backlog attempting to send because no connection became available (2000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). ConnectTimeout, command=GET, timeout: 2000, inst: 0, qu: 1, qs: 0, aw: False, bw: SpinningDown, rs: NotStarted, ws: Idle, in: 0, last-in: 0, cur-in: 0, sync-ops: 43, async-ops: 2, serverEndpoint: internalcache.redis.cache.windows.net:6380, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: VNEXT-SE(SE.Redis-v2.7.27.49176), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=2,Free=32765,Min=4,Max=32767), POOL: (Threads=5,QueuedItems=0,CompletedItems=9838,Timers=17), v: 2.7.27.49176 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts) ---> StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). ConnectTimeout --- End of inner exception stack trace --- at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor1 processor, ServerEndPoint server, T defaultValue) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 2105 at StackExchange.Redis.RedisBase.ExecuteSync[T](Message message, ResultProcessor1 processor, ServerEndPoint server, T defaultValue) in //src/StackExchange.Redis/RedisBase.cs:line 62 at StackExchange.Redis.RedisDatabase.StringGetWithExpiry(RedisKey key, CommandFlags flags) in //src/StackExchange.Redis/RedisDatabase.cs:line 3107 a

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported StackExchange.Redis exception and the referenced timeout guidance, then inspect the stack-trace entry points in ConnectionMultiplexer.cs, RedisBase.cs, and RedisDatabase.cs. The issue provides no repository file, reproduction, or confirmed cause, so completion would require a reproducible .NET 8 failure and an identified connectivity fix or documented configuration cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, kubernetes, redis
Domain
backend, cloud, databases, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.