These ports are used by clients to communicate with a clustered Azure Cache For Redis nodes and could cause connectivity issues on those ports.

If you're using Istio or any other service mesh, check that your service mesh proxy reserves port 13000-13019 or 15000-15019.

A pod running the client application can be affected by other pods running on the same node and throttle Redis connections or IO operations.

If your client application is hosted on Kubernetes, check that the pod running the client application or the cluster nodes aren't under memory/CPU/Network pressure.

For more information on sizing per client connections, see Azure Cache for Redis performance. Number of connected clientsĬheck if the Max aggregate for Connected Clients metric is close or higher than the maximum number of allowed connections for a particular cache size. To minimize the effects of failovers, see Connection resilience. You can validate by checking the Errors (Type: Failover) metric on your portal. Your application can be negatively affected during the maintenance. Sometimes, your cache undergoes a planned or an unplanned server maintenance.

Your client application might have intermittent connectivity issues caused by events such as patching, or spikes in the number of connections. Connectivity issues are divided into two types: intermittent connectivity issues and continuous connectivity issues.

In this article, we provide troubleshooting help for connecting your client application to Azure Cache for Redis.

Tableplus redis