Skip to content
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

5000ms timeout ,unkown reason #2792

Open
qiqisteve opened this issue Sep 8, 2024 · 1 comment
Open

5000ms timeout ,unkown reason #2792

qiqisteve opened this issue Sep 8, 2024 · 1 comment

Comments

@qiqisteve
Copy link

the same server env, golang redis is ok ,dotnet always 5000ms timeout,fix it
2024-09-08 14:25:21.6162|1|ERROR|Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware|An unhandled exception has occurred while executing the request. StackExchange.Redis.RedisTimeoutException: Timeout performing GET (5000ms), next: GET SP:po:2024090814240523061, inst: 1, qu: 0, qs: 8, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 2256, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, sync-ops: 13886, async-ops: 0, serverEndpoint: localhost:6369, conn-sec: 51834.44, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: VM-0-6-ubuntu(SE.Redis-v2.8.12.45748), IOCP: (Busy=0,Free=1000,Min=2,Max=1000), WORKER: (Busy=8,Free=32759,Min=2,Max=32767), POOL: (Threads=8,QueuedItems=8,CompletedItems=226824,Timers=7), v: 2.8.12.45748 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts) 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

@NickCraver
Copy link
Collaborator

How large is the payload that's being retrieved here? Stats to not look off, so it seems like we're waiting on data in the response to come in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants