All of a sudden since the 11th August getting RedisTimeoutException

Hi Clifton Sammut Thank you for reaching out.

If my understanding is correct, you are facing timeout exception error on redis stack exchange suddenly and no code or changes were made. This could be due to the below.

• If you are getting network bound on the server? Following are the max bandwidth we got while testing various sizes of Redis cache. (Following numbers are not guaranteed and is what we got while testing using redis-benchmark.exe running from an Iaas VM against the Azure Redis Cache endpoint)If there are requests that are getting bound by bandwidth, it will take longer for them to complete and thereby cause timeouts. It is recommended to move to a higher cache size to get more bandwidth. Go here for more information on the bandwidth numbers. Cache NameCache SizeGET/sec (Simple GET calls of 1 KB values)Bandwidth (Mbits/sec)C0250 MB6105C11 GB12,200100C22.5 GB24,300200C36 GB48,875400C413 GB61,350500C526 GB112,2751000C653 GB153,2191000+ 
• If you are you getting network bound on the client? Verify you are not getting network bound on you client. Getting Network bound on the client would create a bottleneck and cause timeouts. Moving to a higher VM size on the client to be lined up with the size/speed of the cache would give you the optimal results. You can use the Bandwidth Monitor program to check the bandwidth that you are getting on the client.

Please check the above and let us know if that solve your problem.

Regards,

Oury

Clifton Sammut

We haven't heard back from you and would like to know the status of the above issue. Did you had the chance to check the above comment.

Regards,

Oury

I'd like to +1 this. We have a number of web applications hosted in Azure App Services which are in no way network or resource constrained, and have all started throwing random redis timeouts in healthchecks and actual calls in the last month or so.

StackExchange.Redis.RedisTimeoutException: Timeout awaiting response (outbound=0KiB, inbound=0KiB, 1047ms elapsed, timeout is 500ms), command=PING, next: PING, inst: 0, qu: 0, qs: 0, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in: 0, last-in: 4, cur-in: 0, sync-ops: 0, async-ops: 192, serverEndpoint: elided.redis.cache.windows.net:6380, conn-sec: 901.02, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: pd0sdwk000V97(SE.Redis-v2.6.122.38350), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=3,Free=1020,Min=1,Max=1023), POOL: (Threads=4,QueuedItems=0,CompletedItems=2082062,Timers=16), 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)
   at HealthChecks.Redis.RedisHealthCheck.CheckHealthAsync(HealthCheckContext context, CancellationToken cancellationToken) in /_/src/HealthChecks.Redis/RedisHealthCheck.cs:line 75