尼欧のメモ帳

# Diagnostic timeout exceptions in StackExchange.Redis for Azure Redis Cache ## Problems  >Timeout performing HEXISTS XXX.YYY:OAuthTokenStorages:AccessToken, inst: 267, mgr: Inactive, err: never, queue: 0, qu: 0, qs: 0, qc: 0, wr: 0, wq: 0, in: 0, ar: 0, clientName: RD__________F9, serverEndpoint: Unspecified/xxx.redis.cache.windows.net:6380, keyHashSlot: 1758, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=45,Free=32722,Min=1,Max=32767) (Please take a look at this article for some common client-side issues that can cause timeouts: http://stackexchange.github.io/StackExchange.Redis/Timeouts) ![Picture-02](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIXtx8dOfcuMK6suzswKbCU59eUVEX28TjoRhnwq9xyGm...

There are two SPs perform complicated commands on the same table in our product. Our DBA said he didn't know how to reduce the deadlocks. After Google the key word 'minimizing deadlocks', I found this official document: Key-Range Locking According to above document and this  example , if I select data rows by parameter on non-unique index and then perform some operations, I will only lock these rows. Need some tests......