Problems with Azure Redis Cluster and lettuce versions 4.2.2 and 4.3.0

Hello,

We have an Apache Storm project that uses lettuce to access an Azure Redis Cluster. We were using the lettuce version 4.2.2.Final, and when we tried to scale up the cluster we started receiving these exceptions:

com.lambdaworks.redis.RedisException: java.lang.IllegalArgumentException: Connection to XXX.XX.XXX.XXX:15000 not allowed. This connection point is not known in the cluster viewjava.lang.IllegalArgumentException: Connection to XXX.XX.XXX.XXX:15000 not allowed. This connection point is not known in the cluster viewConnection to XXX.XX.XXX.XXX:15000 not allowed. This connection point is not known in the cluster view Once we restarted the Storm topology, this exception disappeared.

Researching a bit, we saw that there was a newer version, the 4.3.0.Final that had these new properties

This release fixes several issues, provides a streamlined Sorted Sets API and introduces new features for network partition recovery, zero-downtime Redis Cluster reconfiguration and improved resource handling.

So we decided to try that version out. Unfortunately, as soon as we updated our code with this version of lettuce and deployed it into an environment with a Redis cluster, it started to return the same exception (without us modifying the Redis cluster like in the previous time or anything else in the code)

Any ideas what could be the problem?

Thanks, Javier

[mp911de]

Your issue is because of validateClusterNodeMembership and a behavior in Lettuce 4.2.2 and earlier. Disable validateClusterNodeMembership in ClusterClientOptions.

Some background:

You connect using one endpoint that randomly points to an active Cluster node. Lettuce 4.2.2 and earlier replaced the URI of the node with the given (configured) endpoint and considered that address as cluster node address. Since the cluster answers with its internal host name and port (which is different), the membership validation fails. Check out https://github.com/mp911de/lettuce/wiki/Client-options for details, see also #312.

Lettuce 4.3 should have that issue solved but I will investigate on that issue.

[chaimch]

Your issue is because of validateClusterNodeMembership and a behavior in Lettuce 4.2.2 and earlier. Disable validateClusterNodeMembership in ClusterClientOptions.

Some background:

You connect using one endpoint that randomly points to an active Cluster node. Lettuce 4.2.2 and earlier replaced the URI of the node with the given (configured) endpoint and considered that address as cluster node address. Since the cluster answers with its internal host name and port (which is different), the membership validation fails. Check out https://github.com/mp911de/lettuce/wiki/Client-options for details, see also #312.

Lettuce 4.3 should have that issue solved but I will investigate on that issue.

thank you. It’s very useful for me