StackExchange / StackExchange/StackExchange.Redis
Timeout performing EVAL (5000ms) error during local debugging with Azure Cache for Redis resource
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Hi,
We use Azure Cache for Redis version 6.0 for our .net 4.7.2 application and during debugging the application locally we get the error below. We use the same Redis resource for our test environment and it works properly there but during locally we get error. Sometimes it happens more frequently sometimes rarely.
Does anybody have an idea why does it occur?
Thanks in advance.
Timeout performing EVAL (5000ms), next: EVAL, inst: 0, qu: 0, qs: 0, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 0, last-in: 0, cur-in: 0, sync-ops: 200, async-ops: 1, serverEndpoint: {serverEndpoint}, conn-sec: 387,79, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: {clientName} (SE.Redis-v2.7.27.49176)(Microsoft.Web.RedisSessionStateProvider-v5.1.0.0), IOCP: (Busy=0,Free=1000,Min=12,Max=1000), WORKER: (Busy=3,Free=32764,Min=12,Max=32767), 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)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is named. Start with the linked timeout guidance and the supplied EVAL diagnostic, then compare local debugging with the working test environment. The issue does not define a concrete change or a verifiable done condition, so maintainer guidance is needed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100