StackExchange / StackExchange/StackExchange.Redis

Need help understanding Timeout with bw: SpinningDown

Open
#2,582 0 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

Need help understanding Timeout with bw: SpinningDown

This is the redacted Timeout Error:

“Timeout performing HGETALL (5000ms), next: HGETALL {REDACTED_KEY}, inst: 155, qu: 0, qs: 0, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 0, last-in: 0, cur-in: 0, sync-ops: 139378, async-ops: 683, serverEndpoint: {REDACTED_SERVER}, conn-sec: 25024.5, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: {REDACTED_MACHINE_NAME}(SE.Redis-v2.6.122.38350), PerfCounterHelperkeyHashSlot: 12479, IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=30,Free=32737,Min=8,Max=32767), v: 2.6.122.38350 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)”

I've looked at the timeout documentation here: https://stackexchange.github.io/StackExchange.Redis/Timeouts
I couldn't find the reason there. (I have IOCP BUSY=0, in=0, mgr=10/10)

Any help is welcome.

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 linked Timeouts documentation and the redacted timeout diagnostic, especially bw: SpinningDown during HGETALL. Done would require an evidence-based explanation of the reported state or a clearly documented client issue and next steps; no source file or test is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, redis
Domain
backend, databases
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.