The content from this GIST has been moved to official Azure Cache for Redis Documentation. The new location is https://docs.microsoft.com/azure/azure-cache-for-redis/cache-troubleshoot-client
Please update your bookmarks.
Last active
January 6, 2020 17:52
-
-
Save JonCole/db0e90bedeb3fc4823c2 to your computer and use it in GitHub Desktop.
Diagnosing Redis errors caused by issues on the client side
@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.
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
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