Caught this random exception in the wild:
System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was 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 a look at this article for some common client-side issues that can cause timeouts: https://github.com/StackExchange/StackExchange.Redis/tree/master/Docs/Timeouts.md) at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor
1 processor, ServerEndPoint server) at StackExchange.Redis.RedisBase.ExecuteSync[T](Message message, ResultProcessor1 processor, ServerEndPoint server)
Using StackExchange.Redis, deployed on Azure.
From what I can tell from the referenced cached document it looks fine, perhaps the Local-CPU unavailable value is the problem?
Does anyone know what might of caused this to throw?