Skip to content

Instantly share code, notes, and snippets.

@JonCole

JonCole/DiagnoseRedisErrors-ClientSide.md

Last active January 6, 2020 17:52
Show Gist options
  • Star 29 You must be signed in to star a gist
  • Fork 8 You must be signed in to fork a gist
  • Save JonCole/db0e90bedeb3fc4823c2 to your computer and use it in GitHub Desktop.
Save JonCole/db0e90bedeb3fc4823c2 to your computer and use it in GitHub Desktop.
Download ZIP
Diagnosing Redis errors caused by issues on the client side
Raw
DiagnoseRedisErrors-ClientSide.md
@AlanMacdonald
Copy link

But where is the list of error codes for me to compare to what is occurring in the exception? What does wq mean for instance? These error codes are critical info for diagnosing client side error

@merchanf
Copy link

@AlanMacdonald take a look at this: https://azure.microsoft.com/en-us/blog/investigating-timeout-exceptions-in-stackexchange-redis-for-azure-redis-cache/ I couldn't see wq error, but the other attributes are explained.

@kierenj
Copy link

kierenj commented May 8, 2018

I have an exception with an in value of ~16KiB.. however, the client VM is super chunky and capable, and the busy/min are 1 and 4. What else could be causing a backlog like this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment