How to connect to azure managed redis with server port instated of specifying node ports

Hi Tech Support
To connect to your Redis instance using the standard port without specifying individual node ports, you can leverage the Redis service endpoint directly. Azure Managed Redis supports connecting through a single endpoint, which simplifies the connection process by abstracting away the need to manage individual node ports.

The connection string format you would use is:

redis://<redis-server-name>.redis.cache.windows.net:6380

In your case, you should replace <redis-server-name> with your actual Redis server name, which in your case is test-managed-redis.westus2. This ensures you are connecting to the correct instance.

Please check that your client library supports SSL/TLS, as Azure Redis typically uses a secure connection on port 6380. This is the default configuration for Azure Managed Redis, ensuring the security of your data in transit.

Regarding the dynamic nature of node ports, Azure primarily updates the ports during scaling operations or service restarts. To avoid potential connection issues, it’s a good practice to monitor your Redis cluster and handle any changes programmatically, ensuring your application can adapt to these changes as needed.

https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-best-practices-client-libraries#redisson-java
https://learn.microsoft.com/en-us/azure/redis/management-faq#when-should-i-enable-the-non-tls-ssl-port-for-connecting-to-redis

let us know if any help, we will always help as you needed.!

If the comment is helpful, please click "Upvote it".

I am using the following settings for my redisson client config. But with redisson version 3.38.0 onwards it is failing. The older versions it is working fine. I want to use redisson 3.45.0 version with Azure managed Redis. Any suggestions for the client config setting to get it working for the 3.45.0 redisson, would be helpful.

Config redconfig = new Config();
ClusterServersConfig clusterServersConfig = redconfig.useClusterServers();
clusterServersConfig.setTimeout(5000)
        .setIdleConnectionTimeout(30000)
        .setConnectTimeout(15000)
        .setRetryAttempts(3)
        .setRetryInterval(3000)
        .setFailedSlaveReconnectionInterval(15000)
        .setSubscriptionsPerConnection(5)
        .setClientName("redisson")
        .setLoadBalancer(new org.redisson.connection.balancer.RoundRobinLoadBalancer())
        .setSubscriptionConnectionMinimumIdleSize(1)
        .setSubscriptionConnectionPoolSize(50)
        .setSlaveConnectionMinimumIdleSize(2)
        .setSlaveConnectionPoolSize(24)
        .setMasterConnectionMinimumIdleSize(2)
        .setMasterConnectionPoolSize(24)
        .setPingConnectionInterval(60000)
        .setReadMode(ReadMode.MASTER)
        .setSubscriptionMode(SubscriptionMode.MASTER)
        .setScanInterval(2000)
        .setTcpNoDelay(true)
        .setKeepAlive(false)
        .setPassword("Pswd")
        .setDnsMonitoringInterval(5000)
        .setCheckSlotsCoverage(false)
        .addNodeAddress("redis://<redis-server>.<location>.redis.azure.net:10000");


redconfig.setNettyThreads(64);
RedissonClient redisson = Redisson.create(redconfig);

Hi ravibanger

Sure, we will help you out. before proceeding further, I request you to please share error code/ error message which is failing after 3.38.0. did you tried with 3.45.0 version? if you have tried with 3.45.0 version. is it failing with similar error message/code with respect to 3.38.0 version

redission_3.45.1.log redission_3.37.0.log

And below is the java code. We are able to connect with 3.37.0 and not able to connect beyond that.

`

import lombok.extern.slf4j.Slf4j; 
import org.redisson.Redisson; 
import org.redisson.api.RedissonClient; 
import org.redisson.config.ClusterServersConfig; 
import org.redisson.config.Config; 
import org.redisson.config.ReadMode; 
import org.redisson.config.SubscriptionMode;

@ Slf4j 
public class RedissonClusterConnection { 
    public static void main(String[] args) {    
        Config redconfig = new Config();
        ClusterServersConfig clusterServersConfig = redconfig.useClusterServers();
        clusterServersConfig.setTimeout(5000)
            .setIdleConnectionTimeout(30000)
            .setConnectTimeout(15000)
            .setRetryAttempts(3)
            .setRetryInterval(3000)
            .setFailedSlaveReconnectionInterval(15000)
            .setSubscriptionsPerConnection(5)
            .setClientName("redisson")
            .setLoadBalancer(new org.redisson.connection.balancer.RoundRobinLoadBalancer())
            .setSubscriptionConnectionMinimumIdleSize(1)
            .setSubscriptionConnectionPoolSize(50)
            .setSlaveConnectionMinimumIdleSize(2)
            .setSlaveConnectionPoolSize(24)
            .setMasterConnectionMinimumIdleSize(2)
            .setMasterConnectionPoolSize(24)
            .setPingConnectionInterval(60000)
            .setReadMode(ReadMode.MASTER)
            .setSubscriptionMode(SubscriptionMode.MASTER)
            .setScanInterval(2000)
            .setTcpNoDelay(true)
            .setKeepAlive(false)
            .setPassword("passwd")
            .setDnsMonitoringInterval(5000)
            .setCheckSlotsCoverage(false)

            .addNodeAddress("redis://{redis-instance}.redis.azure.net:10000");


    redconfig.setNettyThreads(64);
    RedissonClient redisson = Redisson.create(redconfig);

    // Example usage
    redisson.getBucket("myKey").set("myValue");
    redisson.getBucket("myKey1").set("myValue");
    redisson.getBucket("myKey2").set("myValue");

    System.out.println("Value: " + redisson.getBucket("myKey").get());

    redisson.shutdown();
} 

Hi Tech Support,

Check below steps to troubleshoot the issue:

1. Try using the Redis host with port 10000 for initial connection only and Redisson discovers other nodes.
2. Node ports you are using i.e., 8502, 8503 are dynamic and may change during scaling or failover.
3. Avoid hardcoding node ports; use DNS and keep dnsMonitoringInterval enabled.