Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Connection to X not allowed. This connection point is not known in the cluster view

See original GitHub issue

Lettuce 5.0.2.RELEASE

I’m getting this error:

java.lang.IllegalArgumentException: Connection to 100.123.70.194:6379 not allowed. This connection point is not known in the cluster view
exceptionStackTrace
io.lettuce.core.cluster.PooledClusterConnectionProvider.getConnectionAsync(PooledClusterConnectionProvider.java:359)
io.lettuce.core.cluster.ClusterDistributionChannelWriter.write(ClusterDistributionChannelWriter.java:93)
io.lettuce.core.cluster.ClusterCommand.complete(ClusterCommand.java:56)
io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:563)
io.lettuce.core.protocol.CommandHandler.channelRead(CommandHandler.java:516)
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414)
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945)
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:141)
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:645)
io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:545)
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:499)
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:459)
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
java.lang.Thread.run(Thread.java:844)

Meanwhile, this redis-cluster server seems fine:

100.123.70.194:6379> cluster nodes
8580e93f856ca555d6259a2f2d11b56c3614f80f 100.108.4.2:6379@16379 master - 0 1520926412025 12 connected 0-5460
d64e6009ae6e45cf82b7c0da89f741f5cbc5824c 100.101.254.132:6379@16379 slave 948f85c0e2a4d014e0569ee469dfd259ea02d49e 0 1520926413228 11 connected
664197efc53157e1ec57913c6b76b55818ee8828 100.114.14.132:6379@16379 slave 8580e93f856ca555d6259a2f2d11b56c3614f80f 0 1520926413730 12 connected
24425edffdf69448007c5a5f12d393100368e42d 100.104.184.66:6379@16379 slave 3e0ba54a55cc93d08d39a1b88f3819d5cf3c6f45 0 1520926412226 10 connected
948f85c0e2a4d014e0569ee469dfd259ea02d49e 100.123.70.194:6379@16379 myself,master - 0 1520926412000 11 connected 10923-16383
3e0ba54a55cc93d08d39a1b88f3819d5cf3c6f45 100.112.44.2:6379@16379 master - 0 1520926413529 10 connected 5461-10922

I noticed that I’m getting such errors from time to time now. Not sure what is wrong. Any thoughts?

Issue Analytics

State:
Created 6 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

5reactions

mp911decommented, Mar 13, 2018

That’s a security feature of Lettuce to prevent redirects to nodes that are not (yet) known through CLUSTER NODES. The state can arise if the topology changes while your client has a different view. Lettuce loads the topology upon startup/the first cluster connection. Periodic/adaptive refresh can help or you disable validateClusterNodeMembership in ClusterClientOptions.

2reactions

a34729tcommented, Sep 13, 2018

I have observed this message on Elasticache with Redis 3.XXX when trying to use a recent Lettuce client. Upgrading to 4.XXX does not fix it (I mistakenly reported that it does). Turning off validate cluster node membership does resolve the issue.

Top Results From Across the Web

This connection point is not known in the cluster view

Redis commands like get/set fails when I get this error. Caused by: com.lambdaworks.redis.RedisException: java.lang.IllegalArgumentException: Connection to 10.2 ...

lettuce-io/Lobby - Gitter

IllegalArgumentException: Connection to 10.1.3.53:6379 not allowed. This connection point is not known in the cluster view at org.apache.jasper.servlet.

lettuce集群模式下RedisClusterClient异常:java.lang ... - 博客园

IllegalArgumentException: Connection to x.x.x.x:x not allowed. This connection point is not known in the cluster view. 异常：. 复制代码.

Lettuce Reference Guide

Host and port mappers for Lettuce usage behind connection tunnels/proxies through SocketAddressResolver , see Configuring Client resources.

Cannot retrieve initial cluster partitions from initial URIs ...

The error was coming because I have not installed redis cluster locally on my machine. I solved using these steps.