Timeout SET {Key}, inst: 0, mgr: Inactive, queue: 2, qu = 1, qs = 1, qc = 0, wr = 1/1, in = 0/0

Timeout execution SET {Key}, inst: 0, mgr: Inactive, queue: 2, qu = 1, qs = 1, qc = 0, wr = 1/1, in = 0/0 means it sent one request ( qs), there is another request, which is in the unsent queue (qu), while there is nothing that can be read from the network. there is an active writer meaning that one unsent is not ignored. Basically, there is a request sent and awaiting a response.

A few questions: 1. Does your client work in the same region as the cache? Running it from the dev window will introduce additional latency and cause timeouts. 2. How often do you get an exception? Is it successful at any time? 3. You can also contact azurecache@microsoft.com with your cache name, time (with timezone) where you see timeouts and, if possible, a console application to help reproduce the problem.

Hope this helps, Deepak

details on error codes from this thread: # 83 inst: last slice: 0 mgr: socket manager executes "socket.select", which means it asks the OS to specify a socket to do something; basically: the reader is not actively reading from the network because he does not think there is something to do in the queue: a total of 73 qu operations are performed: 6 of them are in an unresolved queue: they have not yet been written to the outgoing network qs: 67 of them have been sent and are awaiting responses from the qc server: 0 of them have seen responses but have not yet been marked as completely due to waiting in a completion loop wr: there is an active writer (meaning these 6 unsent are not ignored) at: no active readers and zero bytes are readable on the network card