Timeout performing SET {Key}, inst: 0, mgr: Inacti

Question

I am trying to save a 90 KB pdf file into Azure Redis Cache using StackExchange.Redis client. I have converted that file into byte array and tried to save it using stringSet method and received error.

Code:

byte[] bytes = File.ReadAllBytes("ABC.pdf"); cache.StringSet(info.Name, bytes); --> This Line throws exception "Timeout performing SET {Key}, inst: 0, mgr: Inactive, queue: 2, qu=1, qs=1, qc=0, wr=1/1, in=0/0".

Kindly Help.

Answer 1

Timeout performing SET {Key}, inst: 0, mgr: Inactive, queue: 2, qu=1, qs=1, qc=0, wr=1/1, in=0/0 means, it has sent one request (qs), there is another request that's in unsent queue (qu), while there is nothing to be read from the network. there is an active writer meaning the one unsent is not being ignored. Basically, there is a request sent and waiting for the response to be back.

Few questions: 1. Is your client running in the same region as the cache? Running it from your dev box would introduce additional latency and cause timeouts. 2. How often do you get the exception? Does it succeed any time? 3. You can also contact [e-mail] with your cache name, time (with time zone) range in which you see the timeouts and if possible a console app that would help to repro the issue.

Hope this helps, Deepak

details about the error codes from this thread: #83 inst: in the last time slice: 0 commands have been issued mgr: the socket manager is performing "socket.select", which means it is asking the OS to indicate a socket that has something to do; basically: the reader is not actively reading from the network because it doesn't think there is anything to do queue: there are 73 total in-progress operations qu: 6 of those are in unsent queue: they have not yet been written to the outbound network qs: 67 of those have been sent and are awaiting responses from the server qc: 0 of those have seen replies but have not yet been marked as complete due to waiting on the completion loop wr: there is an active writer (meaning - those 6 unsent are not being ignored) in: there are no active readers and zero bytes are available to be read on the NIC