Troubleshoot Redis timeouts
Redis timeouts (RedisTimeoutException
) occur due to various conditions caused by either the server or the client. This topic helps you to find answers for some of the most common timeout scenarios. For more information, you can also refer to Github and Microsoft Azure documentation.
Server- and client-side issues
Learn how to solve issues that occur because of an Azure Cache for Redis condition, or the virtual machine(s) hosting it.
Possible solutions for infrastructure-related causes:
Cause |
Solution |
---|---|
Bandwidth/size limits |
Monitor Redis Server metrics to check whether you have reached bandwidth/size limits. Possible solutions:
|
High client CPU/memory/bandwidth usage |
High CPU, memory, or bandwidth usage can cause the request to not be processed within the
|
Server and client application are not in the same region in Azure |
We recommend that you have the cache and the client in the same Azure region. For example, timeouts might occur when your cache is in East US but the client is in West US and the request does not complete within the |
Application issues
High load can cause RedisTimeoutException
to occur due to a combination of reasons. Try to adjust your application setup/load to solve the problem.
Possible solutions for application-related causes:
Cause |
Solution |
---|---|
Thread limits |
If the Important Do not make changes directly to the configuration files. Instead, you must create a patch file that performs the required changes during runtime.
|
Too many requests |
The Possible solution:
|
Low values for |
The Sitecore Redis session state provider uses configuration settings named operationTimeoutInMilliseconds and retryTimeoutInMilliseconds for operations. If a call does not complete in the time specified, the Redis client throws a timeout error. Possible solution:
|