SETNX Timeout with StackExchange.Redis -
caught random exception in wild:
system.web.httpunhandledexception (0x80004005): exception of type 'system.web.httpunhandledexception' thrown. ---> system.timeoutexception: timeout performing setnx geoip.[redacted], inst: 1, mgr: inactive, err: never, queue: 2, qu: 0, qs: 2, qc: 0, wr: 0, wq: 0, in: 0, ar: 0, clientname: prd-vm-web-1, serverendpoint: unspecified/[redacted].redis.cache.windows.net:6380, keyhashslot: 3519, iocp: (busy=0,free=1000,min=2,max=1000), worker: (busy=1,free=32766,min=2,max=32767), local-cpu: unavailable (please take @ article common client-side issues can cause timeouts: https://github.com/stackexchange/stackexchange.redis/tree/master/docs/timeouts.md) @ stackexchange.redis.connectionmultiplexer.executesyncimpl[t](message message, resultprocessor
1 processor, serverendpoint server) @ stackexchange.redis.redisbase.executesync[t](message message, resultprocessor1 processor, serverendpoint server)
using stackexchange.redis, deployed on azure.
from can tell referenced cached document looks fine, perhaps local-cpu unavailable value problem?
does know might of caused throw?
when @ errors receiving, see timeout errors busy value greater min iocp or worker threadpool? if so, threadpool throttling can cause. happens under bursty scenarios. accompanied high cpu, can cause timeouts. threadpool throttling explained here: https://gist.github.com/joncole/e65411214030f0d823cb#file-threadpool-md.
also, here best practices: https://gist.github.com/joncole/925630df72be1351b21440625ff2671f#best-practices-for-azure-redis
Comments
Post a Comment