Validate that the Inbound and Outbound rules meet the requirement.When the client application is in a different VNet from your Azure Cache For Redis, both VNets must have VNet peering enabled within the same Azure region.Ensure that the client host machine is in the same virtual network as the Azure Cache For Redis.Check if a virtual network is assigned to your cache from the " Virtual Network" section under the Settings on the Resource menu of the Azure portal. Steps to check your virtual network configuration: Confirming ensures no drop in connectivity. You can confirm the number of sent packets is equal to the received packets. If redis-cli is unable to connect, you can test connectivity using PSPING in PowerShell. For more information on CLI, Use the Redis command-line tool with Azure Cache for Redis. The following sections offer suggestions on how to make sure your cache is configured correctly. If your application can't connect to your Azure Cache for Redis, it's possible some configuration on the cache isn't set up correctly. See Connection stalls lasting for 15 minutes. Using optimistic TCP settings in Linux might cause client applications to experience connectivity issues. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |