StackExchange / StackExchange/StackExchange.Redis

Timeout awaiting response

Open
#2,673 3 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

Hey team!

Now and then we encounter "Timeout awaiting response"
We're hosting our env on Azure and using Azure Cache for Redis
Tier: Standard 1 GB

Here is the error message:
Timeout awaiting response (outbound=0KiB, inbound=0KiB, 5884ms elapsed, timeout is 5000ms), command=GET, next: GET #, inst: 0, qu: 0, qs: 0, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 0, last-in: 210, cur-in: 0, sync-ops: 0, async-ops: 18238, serverEndpoint: #, conn-sec: 22769.29, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: client(SE.Redis-v2.7.20.59961), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=1,Free=32766,Min=1,Max=32767), POOL: (Threads=2,QueuedItems=0,CompletedItems=460840,Timers=10), v: 2.7.20.59961 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)

The issue occurred at 23:49:36.5374749

Server load:
image
CPU:
image
Cache hit:
image
Cache read:
image
Total keys:
image

Would it be at all possible to lend a helping hand? We would highly appreciate your help.
Thanks in advance!

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 timeout diagnostics article linked in the error and review the Azure Cache for Redis metrics and screenshots provided. The issue does not identify a repository file, test, or specific code change; it would need a confirmed cause and a reproducible fix or documented guidance before completion could be defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, redis
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.