Sprintboot 2.3.1链接redis，链接redis 127.0.0.1错误异常查找

最新推荐文章于 2024-05-07 10:51:40 发布
最新推荐文章于 2024-05-07 10:51:40 发布
阅读量1k 收藏
点赞数
分类专栏： SpringBoot Redis
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/zzhongcy/article/details/107818442
版权

介绍

    以前使用Sprintboot链接redis使用都很正常，但是最近申请了一套服务器，在Sprintboot链接新redis集群时，Sprintboot日志报链接redis集群失败，日志里显示奇怪的redis IP，例如127.0.0.1。

日志如下：

2020-08-05 16:46:02.388 [http-nio-5252-exec-2] DEBUG io.lettuce.core.EpollProvider - Starting without optional epoll library
2020-08-05 16:46:02.391 [http-nio-5252-exec-2] DEBUG io.lettuce.core.KqueueProvider - Starting without optional kqueue library
2020-08-05 16:46:02.393 [http-nio-5252-exec-2] DEBUG i.l.c.r.DefaultEventLoopGroupProvider - Allocating executor io.netty.channel.nio.NioEventLoopGroup
2020-08-05 16:46:02.393 [http-nio-5252-exec-2] DEBUG i.l.c.r.DefaultEventLoopGroupProvider - Creating executor io.netty.channel.nio.NioEventLoopGroup
2020-08-05 16:46:02.394 [http-nio-5252-exec-2] DEBUG i.n.c.MultithreadEventLoopGroup - -Dio.netty.eventLoopThreads: 8
2020-08-05 16:46:02.399 [http-nio-5252-exec-2] DEBUG io.netty.channel.nio.NioEventLoop - -Dio.netty.noKeySetOptimization: false
2020-08-05 16:46:02.399 [http-nio-5252-exec-2] DEBUG io.netty.channel.nio.NioEventLoop - -Dio.netty.selectorAutoRebuildThreshold: 512
2020-08-05 16:46:02.402 [http-nio-5252-exec-2] DEBUG i.l.c.r.DefaultEventLoopGroupProvider - Adding reference to io.netty.channel.nio.NioEventLoopGroup@49610338, existing ref count 0
2020-08-05 16:46:02.422 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9001
2020-08-05 16:46:02.426 [http-nio-5252-exec-2] DEBUG io.netty.channel.DefaultChannelId - -Dio.netty.processId: 150361 (auto-detected)
2020-08-05 16:46:02.429 [http-nio-5252-exec-2] DEBUG io.netty.util.NetUtil - -Djava.net.preferIPv4Stack: false
2020-08-05 16:46:02.429 [http-nio-5252-exec-2] DEBUG io.netty.util.NetUtil - -Djava.net.preferIPv6Addresses: false
2020-08-05 16:46:02.431 [http-nio-5252-exec-2] DEBUG io.netty.util.NetUtil - Loopback interface: lo (lo, 127.0.0.1)
2020-08-05 16:46:02.432 [http-nio-5252-exec-2] DEBUG io.netty.util.NetUtil - /proc/sys/net/core/somaxconn: 4096
2020-08-05 16:46:02.432 [http-nio-5252-exec-2] DEBUG io.netty.channel.DefaultChannelId - -Dio.netty.machineId: 00:50:56:ff:fe:85:3d:80 (auto-detected)
2020-08-05 16:46:02.462 [http-nio-5252-exec-2] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.allocator.type: pooled
2020-08-05 16:46:02.462 [http-nio-5252-exec-2] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.threadLocalDirectBufferSize: 0
2020-08-05 16:46:02.462 [http-nio-5252-exec-2] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.maxThreadLocalCharBufferSize: 16384
2020-08-05 16:46:02.474 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9002
2020-08-05 16:46:02.475 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9003
2020-08-05 16:46:02.485 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9004
2020-08-05 16:46:02.486 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9005
2020-08-05 16:46:02.486 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9006
2020-08-05 16:46:02.489 [lettuce-nioEventLoop-4-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.maxCapacityPerThread: 4096
2020-08-05 16:46:02.489 [lettuce-nioEventLoop-4-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.maxSharedCapacityFactor: 2
2020-08-05 16:46:02.489 [lettuce-nioEventLoop-4-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.linkCapacity: 16
2020-08-05 16:46:02.489 [lettuce-nioEventLoop-4-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.ratio: 8
2020-08-05 16:46:02.489 [lettuce-nioEventLoop-4-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.delayedQueue.ratio: 8
2020-08-05 16:46:02.499 [lettuce-nioEventLoop-4-1] DEBUG io.netty.buffer.AbstractByteBuf - -Dio.netty.buffer.checkAccessible: true
2020-08-05 16:46:02.499 [lettuce-nioEventLoop-4-1] DEBUG io.netty.buffer.AbstractByteBuf - -Dio.netty.buffer.checkBounds: true
2020-08-05 16:46:02.499 [lettuce-nioEventLoop-4-1] DEBUG i.n.u.ResourceLeakDetectorFactory - Loaded default ResourceLeakDetector: io.netty.util.ResourceLeakDetector@3424791d
2020-08-05 16:46:02.531 [lettuce-nioEventLoop-4-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9002: Success
2020-08-05 16:46:02.532 [lettuce-nioEventLoop-4-4] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9004: Success
2020-08-05 16:46:02.533 [lettuce-nioEventLoop-4-3] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9003: Success
2020-08-05 16:46:02.535 [lettuce-nioEventLoop-4-1] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9001: Success
2020-08-05 16:46:02.539 [lettuce-nioEventLoop-4-4] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.539 [lettuce-nioEventLoop-4-3] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.540 [lettuce-nioEventLoop-4-1] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.541 [lettuce-nioEventLoop-4-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.553 [lettuce-nioEventLoop-4-1] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9005: Success
2020-08-05 16:46:02.553 [lettuce-nioEventLoop-4-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9006: Success
2020-08-05 16:46:02.561 [lettuce-nioEventLoop-4-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.561 [lettuce-nioEventLoop-4-1] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.563 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null'], commandType=io.le
ttuce.core.protocol.Command]
2020-08-05 16:46:02.565 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null'], commandType=io.le
ttuce.core.protocol.Command]
2020-08-05 16:46:02.566 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null'], commandType=io.le
ttuce.core.protocol.Command]
2020-08-05 16:46:02.573 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null'], commandType=io.le
ttuce.core.protocol.Command]
2020-08-05 16:46:02.574 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null'], commandType=io.le
ttuce.core.protocol.Command]
2020-08-05 16:46:02.574 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null'], commandType=io.le
ttuce.core.protocol.Command]
2020-08-05 16:46:02.575 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=INFO, output=StatusOutput [output=null, error='null'], commandType=io.lettu
ce.core.protocol.Command]
2020-08-05 16:46:02.575 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=INFO, output=StatusOutput [output=null, error='null'], commandType=io.lettu
ce.core.protocol.Command]
2020-08-05 16:46:02.575 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=INFO, output=StatusOutput [output=null, error='null'], commandType=io.lettu
ce.core.protocol.Command]
2020-08-05 16:46:02.577 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=INFO, output=StatusOutput [output=null, error='null'], commandType=io.lettu
ce.core.protocol.Command]
2020-08-05 16:46:02.585 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=INFO, output=StatusOutput [output=null, error='null'], commandType=io.lettu
ce.core.protocol.Command]
2020-08-05 16:46:02.585 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command TimedAsyncCommand [type=INFO, output=StatusOutput [output=null, error='null'], commandType=io.lettu
ce.core.protocol.Command]
2020-08-05 16:46:02.627 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9006
2020-08-05 16:46:02.633 [lettuce-nioEventLoop-4-3] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9006: Success
2020-08-05 16:46:02.635 [lettuce-nioEventLoop-4-3] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.635 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9003
2020-08-05 16:46:02.636 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 127.0.0.1:9006
2020-08-05 16:46:02.636 [lettuce-nioEventLoop-4-4] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9003: Success
2020-08-05 16:46:02.637 [lettuce-nioEventLoop-4-4] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.638 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9002
2020-08-05 16:46:02.639 [http-nio-5252-exec-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 127.0.0.1:9005
2020-08-05 16:46:02.640 [lettuce-nioEventLoop-4-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9002: Success
2020-08-05 16:46:02.640 [lettuce-nioEventLoop-4-2] DEBUG io.lettuce.core.RedisChannelHandler - dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lett
uce.core.protocol.Command]
2020-08-05 16:46:02.643 [lettuce-nioEventLoop-4-1] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 127.0.0.1:9006: 127.0.0.1:9006
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:9006
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:9006
Caused by: java.net.ConnectException: Connection refused
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
        at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:702)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Thread.java:748)
2020-08-05 16:46:02.643 [lettuce-nioEventLoop-4-1] DEBUG io.lettuce.core.RedisChannelHandler - close()
2020-08-05 16:46:02.643 [lettuce-nioEventLoop-4-1] DEBUG io.lettuce.core.RedisChannelHandler - closeAsync()
2020-08-05 16:46:02.644 [lettuce-nioEventLoop-4-1] DEBUG i.l.c.c.t.ClusterTopologyRefresh - Unable to connect to [127.0.0.1:9006]: Connection refused: /127.0.0.1:9006
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:9006
Caused by: java.net.ConnectException: Connection refused
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
        at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:702)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Thread.java:748)
2020-08-05 16:46:02.646 [lettuce-nioEventLoop-4-3] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 127.0.0.1:9005: 127.0.0.1:9005
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:9005
Caused by: java.net.ConnectException: Connection refused
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
        at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:702)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Thread.java:748)
2020-08-05 16:46:02.647 [lettuce-nioEventLoop-4-3] DEBUG io.lettuce.core.RedisChannelHandler - close()
2020-08-05 16:46:02.647 [lettuce-nioEventLoop-4-3] DEBUG io.lettuce.core.RedisChannelHandler - closeAsync()

现象

本来是打算链接redis集群：

10.10.10.142:9001，10.10.10.142:9002，10.10.10.142:9003，10.10.10.142:9004，10.10.10.142:9005，10.10.10.142:9006

日志显示也链接成功了：

2020-08-05 16:46:02.531 [lettuce-nioEventLoop-4-2] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9002: Success
2020-08-05 16:46:02.532 [lettuce-nioEventLoop-4-4] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9004: Success
2020-08-05 16:46:02.533 [lettuce-nioEventLoop-4-3] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9003: Success
2020-08-05 16:46:02.535 [lettuce-nioEventLoop-4-1] DEBUG io.lettuce.core.RedisClient - Connecting to Redis at 10.10.10.142:9001: Success

为什么会连接IP为127.0.0.1的redis集群呢？如下：

127.0.0.1:9001，127.0.0.1:9002，127.0.0.1:9003，127.0.0.1:9004，127.0.0.1:9005，127.0.0.1:9006

重要的是：但是端口是正确的。

查找原因

登录redis机子，查看redis集群状态：

$ ../bin/redis-cli -p 9001 cluster nodes
53b81ff738ce1f0368ee2ebd2253de99982aaa6c 127.0.0.1:9002@19002 master - 0 1596607175841 2 connected 5461-10922
db99d0ec79054e58bdb6a2d8da2c29bd4cd7f439 127.0.0.1:9006@19006 slave ac8096ff06260d23b75bcb130edd1710a50ba25e 0 1596607177846 6 connected
b55b3d8c0828101ba500952ab9879488f7d871ae 127.0.0.1:9005@19005 slave cdf1a8f1475aca64a5050e310b6b3c6f79e6839d 0 1596607178848 5 connected
cdf1a8f1475aca64a5050e310b6b3c6f79e6839d 127.0.0.1:9003@19003 master - 0 1596607176842 3 connected 10923-16383
ac8096ff06260d23b75bcb130edd1710a50ba25e 127.0.0.1:9001@19001 myself,master - 0 1596607177000 1 connected 0-5460
ae33879808984f2e58a0f44dde7b1fe628e5fc21 127.0.0.1:9004@19004 slave 53b81ff738ce1f0368ee2ebd2253de99982aaa6c 0 1596607177000 4 connected

哈哈，这里居然出现了127.0.0.1信息。

于是立马关闭集群，清空data，再用IP 10.10.10.142创建集群：

./bin/redis-cli --cluster create 10.10.10.142:9001 10.10.10.142:9002 10.10.10.142:9003 10.10.10.142:9004 10.10.10.142:9005 10.10.10.142:9006 --cluster-replicas 1

查看集群状态：

$ ../bin/redis-cli -c -p 9001 cluster nodes
e08676e289e291f8dc85ad8d344e6f83f9c27b82 10.10.10.142:9005@19005 slave fc0af031e9399d61a9b1d49543c62dcce6535e8c 0 1596614376805 5 connected
ff664dc29addc758000b696d517c939af2dafbcd 10.10.10.142:9004@19004 slave e6fb1c309c8ef0ea036745f4355ef0c45220f275 0 1596614377806 4 connected
6ef689a2592463653cab7dac82aa2d5935d2daf4 10.10.10.142:9006@19006 slave 61ffc9d221519afb92fd721250abf177cb57df26 0 1596614375000 6 connected
e6fb1c309c8ef0ea036745f4355ef0c45220f275 10.10.10.142:9003@19003 master - 0 1596614374802 3 connected 10923-16383
fc0af031e9399d61a9b1d49543c62dcce6535e8c 10.10.10.142:9001@19001 myself,master - 0 1596614375000 1 connected 0-5460
61ffc9d221519afb92fd721250abf177cb57df26 10.10.10.142:9002@19002 master - 0 1596614376000 2 connected 5461-10922

可以看到，IP不是127.0.0.1了

验证

再查看Sprintboot日志，没有出现链接redis集群报错了。

结论

Sprintboot再链接到redis节点后，会更具redis节点获取redis cluster集群信息，这个时候你配置的redis信息以及被替换了，所以创建redis集群时最好使用真实IP。

本地创建和本地程序访问redis，创建集群可以用 127.0.0.1
但是其他机子访问本机redis，创建集群必须用IP，例如10.10.10.142:9001

 

zzhongcy
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
java.io.IOException: 应用程序没有调用 WSAStartup，或者 WSAStartup 失败。
chengcaiok的博客
05-17 3293
2019-05-17 16:38:26.387 [lettuce-nioEventLoop-4-1] INFO io.lettuce.core.protocol.CommandHandler - null Unexpected exception during request: java.io.IOException: 应用程序没有调用 WSAStartup，或者 WSAStartup 失败。 ...
spring boot整合redis集群，连接虚拟机redis集群，Unable to connect to 127
嘎嘎的博客
12-16 2万+
spring boot整合redis集群 最近的一个个人项目中使用到redis集群，redis集群的搭建环境使用同一台虚拟机，创建集群的命令是 redis-cli --cluster create 127.0.0.1:6379 127.0.0.1:6380 127.0.0.1:6381 127.0.0.1:6382 127.0.0.1:6383 127.0.0.1:6384 --cluster-r...
连接Redis集群报 Unable to connect to 127.0.0.1:7008 错误
热门推荐
我的Java之路,关注Java技术的发展
09-16 3万+
连接Redis集群报 -MOVED 9707 127.0.0.1:7002 错误 错误现象 application.yaml中配置如下 spring: cache: type: redis redis: time-to-live: 60000 redis: cluster: max-redirects: 3 nodes: ...
springboot整合redis一直报远程主机强迫关闭了一个现有的连接
最新发布
Java领域优秀创作者
05-07 706
通过合理配置Redis服务器和客户端的连接设置，可以有效解决“远程主机强迫关闭了一个现有的连接”问题。关键在于正确配置timeout和参数，同时确保网络环境的稳定性和客户端的连接设置。希望通过本文的详细讲解，能帮助你解决Spring Boot整合Redis时遇到的连接问题。如果还有其他疑问或问题，欢迎进一步探讨。
记一次用arthas排查jvm中CPU占用过高问题
Candyz7的博客
09-02 1899
其实这个线程名称已经能定位到具体某个方向的问题了，所以线程名称的定义需要有意义 为了方便排查问题。而内存是正常的，可以认为大概率是某个线程占用了计算资源 导致的。.targetType(String.class) // 目标类型。控制台中显示了当前机器上jvm进程列表 输入需要排查的jvm进程号即可进入监控命令模式。排查jvm中CPU占用过高问题。这工具屌爆了 碾压我目前使用的全部JVM工具。的方法找出占用资源的线程PID 方法top -Hp方法参考。这个是解决问题个人觉得最重要的一步。
Springboot集成Redis常见的报错和解决方案
后端开发
06-14 5805
本文主要解决以下俩个问题： 1.io.lettuce.core.protocol.CommandHandler : null Unexpected exception during request: java.io.IOException: 2.io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 16777216 byte(s) of direct memory (used: 1073741824, max: 1073
redis可视化链接工具---fastoredis-2.3.1
08-16
官网下载老坑了，半天都不见动一下，特意提供fastoredis-2.3.1-x86_64安装包给各位程序猿，欢迎大家下载，即装即用！！！
springboot2.3.1替换为其他的嵌入式servlet容器的详细方法
08-18
Spring Boot 2.3.1 替换嵌入式 Servlet 容器的详细方法 在 Spring Boot 2.3.1 中，默认情况下使用 Tomcat 作为嵌入式 Servlet 容器，但是如果我们想使用其他的Servlet容器，例如 Jetty 或 Netty，该如何实现呢？...
Redis Viewer-2.3.1.exe
10-08
Redis Viewer-2.3.1
详解SSH框架和Redis的整合
09-09
1. **相关Jar文件**：为了实现SSH与Redis的整合，需要引入Redis客户端Jedis的jar包（如jedis-2.3.1.jar）以及Spring对Redis支持的相关jar包（如spring-data-redis-1.3.4.RELEASE.jar）。此外，还需要连接池管理的库...
opencv2.3.1 静态链接库 winxp+vs2008
05-08
opencv2.3.1 静态链接库 winxp+vs2008，针对windowsXP系统，vs2008环境生成的opencv2.3.1静态链接库，摆脱dll的使用，包括Debug版本，Release版本。
springboot 使用 lettuce连接redis 集群，master宕机，自动更新拓扑
qq_25240909的博客
08-21 4290
求助！！！求助！！！ springboot 使用 lettuce连接redis 集群，master宕机，自动更新拓扑无效 请各路大神不吝指教，万分感谢。 cluster集群方式为3主3从。 测试方式为不断的写入数据过程中，将其中一台master节点宕掉。 for (int i = 0; i < Integer.MAX_VALUE; i++) { stringRedisTemplate.opsForValue().set((i + ""), i + "", 1, TimeUnit.HOURS);
spring boot redis 集群下拓扑不自动刷新的问题
liukaixiang000的博客
12-25 5382
spring boot redis 集群下拓扑不自动刷新的问题 最近使用spring boot连接redis三主三从集群，但是当一台redis节点挂掉后，spring boot程序依然报错，command timeout 异常。网上搜索，看源码，折腾了半天，才搞定。 环境 spring boot 版本为2.1.8.RELEASE，spring-boot-starter-data-redis为2.1...
io.lettuce.core.cluster.PartitionSelectorException: Cannot determine a partition to read for slot xx
AVATAR
02-21 1898
io.lettuce.core.cluster.PartitionSelectorException: Cannot determine a partition to read for slot xx
Springboot 集成 Redis集群配置公网IP连接报私网IP连接失败问题
冰夜翎博客
10-10 1310
创建6个配置文件：redis-6381.conf,redis-6382.conf,redis-6383.conf,redis-6384.conf,redis-6385.conf,手动指定了公网ip后，Redis集群中的节点会通过公网IP进行通信，也就是外网访问。让Redis暴露公网IP其实在redis.conf配置文件里是能找到的，这里我们可以手动指定Redis的公网IP、端口以及总线端口(默认服务端口加10000)。根据以上配置修改每一个redis节点的配置，注意端口不能相同。
记一次使用redis stream创建的消息队列时，导致java服务的CPU、Memory过高的问题
tikaber的博客
04-08 2212
首先通过jstack查看cpu过高的原因，进一步定位问题，由于本人对DefaultStreamMessageListenerContainer源码有操作，遂在服务中重写了该类的内容，由下方异常可以看出com.bot.base.biz.redis.rediesmq.stream.AIDefaultStreamMessageListenerContainer.lambda$getReadFunction$17(AIDefaultStreamMessageListenerContainer.java:255)出现
Linux学习-Redis哨兵
丢爸
11-10 660
redis通过sentinel解决高并发或因服务器宕机引起的redis不可用问题
springboot+redis主从复制、哨兵、读写分离
Remember_Z的博客
03-02 6138
redis安装、主从配置、哨兵配置、以及在springboot中的集成、读写分离等。
Spring整合Redisson(全是步骤，没有原理）
一歪风的博客
03-07 1630
在applicationContext.xml文件中添加对应redis模式的配置（单机，哨兵和集群模式）
SpringBoot工程中mybatis 2.3.1版本对应的分页插件的依赖
07-14
对于 MyBatis 2.3.1 版本的 Spring Boot 工程，可以使用 PageHelper 作为分页插件。以下是添加 PageHelper 分页插件的依赖配置示例： ```xml <groupId>com.github.pagehelper</groupId> <artifactId>pagehelper-...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值