Linux学习-Redis哨兵

最新推荐文章于 2022-12-24 23:57:43 发布
最新推荐文章于 2022-12-24 23:57:43 发布
阅读量661 收藏
点赞数
分类专栏： Linux 文章标签： linux 学习 redis
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/xuwenpeng/article/details/127778925
版权
Redis哨兵
Redis提供了哨兵(Sentinel)机制来实现主从集群的自动故障恢复
哨兵的作用：
1.监控：Sentinel会不断检查master和slave是否按预期工作
2.自动故障恢复：如果master故障，Sentinel会将一个slave提升为master,当故障实例恢复后也以新的master为主
3.通知：Sentinel充当Redis客户端的服务发现来源，当集群发生故障转移时，会将最新信息推送给Redis客户端


服务器状态监控
Sentinel基于心跳机制监控服务状态，每隔一秒向集群的每个实例发送ping命令
1.主观下线：如果某Sentinel节点发现某实例未在规定时间响应，则认为该实例主观下线
2.客观下线：若超过指定数量(quorum)的sentinel都认为该实例主观下线，则该实例客观下线，quorum值超过Sentinel实例数量的一半

如何选举新的master?
1.首先判断slave节点与master节点断开时间长短，如果超过指定值(down-after-milliseconds*10)则会排除该slave节点
2.然后判断slave节点的slave-priority值，越小优先级越高，如果是0则永不参与选举
3.如果slave-priority一样，则判断slave节点的offset值，越大说明数据越新，优先级越高
4最后是判断slave节点的运行id大小，越小优先级越高

如何进行故障转移？
1.Sentinel给备选的slave1节点发送slaveof no one命令，让该节点成为新master
2.Sentinel给所有其它slave发送slaveof 192.168.115.129 7002命令，让这些slave成为新master的从节点，开始从新master上同步数据
3.Sentinel将故障节点标记为slave，当故障节点恢复后自动成为新的master的slave节点
搭建哨兵
#1.在/opt下创建三个目录s1,s2,s3
[root@redis ~]# cd /opt
[root@redis opt]# ls
7001  7002  7003
[root@redis opt]# mkdir s{1..3}
[root@redis opt]# ls
7001  7002  7003  s1  s2  s3
#2.创建配置文件
[root@redis opt]# vim s1/sentinel.conf
#当前sentinel实例的端口
port 27001
sentinel announce-ip 192.168.115.129
`指定主节点信息，
  mymaster：主节点名称，自定义，任意写
  192.168.115.129 7001：主节点的IP和端口
  2：选举master时的quorum值
`
sentinel monitor mymaster 192.168.115.129 7001 2
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 60000
dir "/opt/s1"
[root@redis opt]# echo s2 s3 | xargs -t -n 1 cp s1/sentinel.conf 
cp s1/sentinel.conf s2 
cp s1/sentinel.conf s3 
[root@redis opt]# sed -i -e 's/27001/27002/g' -e 's/s1/s2/g' s2/sentinel.conf 
[root@redis opt]# cat s2/sentinel.conf
port 27002
sentinel announce-ip 192.168.115.129
sentinel monitor mymaster 192.168.115.129 7001 2
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 60000
dir "/opt/s1"
[root@redis opt]# sed -i -e 's/27001/27003/g' -e 's/s1/s3/g' s3/sentinel.conf
使用哨兵
#在服务器上启动所有哨兵和redis
[root@redis opt]# redis-server 7001/redis.conf
[root@redis opt]# redis-server 7002/redis.conf
[root@redis opt]# redis-server 7003/redis.conf
[root@redis opt]# redis-sentinel s1/sentinel.conf
[root@redis opt]# redis-sentinel s2/sentinel.conf
[root@redis opt]# redis-sentinel s3/sentinel.conf
#通过spring-data-redis中redisTemplate使用哨兵
#在项目配置文件中添加sentinel配置信息application.yml
spring:
  redis:
    sentinel:
      master: mymaster
      nodes:
        - 192.168.115.129:27001
        - 192.168.115.129:27002
        - 192.168.115.129:27003
#配置主从读写分离
@Bean
    public LettuceClientConfigurationBuilderCustomizer clientConfigurationBuilderCustomizer() {
        return clientConfigurationBuilder -> clientConfigurationBuilder.readFrom(ReadFrom.REPLICA_PREFERRED);
    }
#ReadFrom配置读取策略，是一个枚举
1.MASTER：从主节点读取
2.MASTER_PREFERRED：优先从master节点读取，master不可用，才读取replica
3.REPLICA：从slave(replica)节点读取
4.REPLICA_PREFERRED；优先从slave(replica)节点读取，所有的slave都不可用时从master读取
#查看idea输出日志
1.设置键值
11-10 09:20:45:261 DEBUG 7512 --- [nio-8080-exec-9] io.lettuce.core.RedisChannelHandler      : dispatching command AsyncCommand [type=SET, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:20:45:261 DEBUG 7512 --- [nio-8080-exec-9] i.l.c.m.MasterSlaveConnectionProvider    : getConnectionAsync(WRITE)
11-10 09:20:45:261 DEBUG 7512 --- [nio-8080-exec-9] io.lettuce.core.RedisChannelHandler      : dispatching command AsyncCommand [type=SET, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:20:45:261 DEBUG 7512 --- [nio-8080-exec-9] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0xa8219472, /192.168.115.1:61220 -> /192.168.115.129:7001, epid=0xd] write() writeAndFlush command AsyncCommand [type=SET, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:20:45:261 DEBUG 7512 --- [nio-8080-exec-9] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0xa8219472, /192.168.115.1:61220 -> /192.168.115.129:7001, epid=0xd] write() done
11-10 09:20:45:261 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0xa8219472, /192.168.115.1:61220 -> /192.168.115.129:7001, chid=0x33] write(ctx, AsyncCommand [type=SET, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command], promise)
11-10 09:20:45:263 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandEncoder  : [channel=0xa8219472, /192.168.115.1:61220 -> /192.168.115.129:7001] writing command AsyncCommand [type=SET, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:20:45:265 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0xa8219472, /192.168.115.1:61220 -> /192.168.115.129:7001, chid=0x33] Received: 5 bytes, 1 commands in the stack
11-10 09:20:45:265 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0xa8219472, /192.168.115.1:61220 -> /192.168.115.129:7001, chid=0x33] Stack contains: 1 commands
11-10 09:20:45:265 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.RedisStateMachine      : Decode AsyncCommand [type=SET, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:20:45:265 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.RedisStateMachine      : Decoded AsyncCommand [type=SET, output=StatusOutput [output=OK, error='null'], commandType=io.lettuce.core.protocol.Command], empty stack: true
2.查看键值
11-10 09:22:33:885 DEBUG 7512 --- [nio-8080-exec-2] io.lettuce.core.RedisChannelHandler      : dispatching command AsyncCommand [type=GET, output=ValueOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:22:33:885 DEBUG 7512 --- [nio-8080-exec-2] i.l.c.m.MasterSlaveConnectionProvider    : getConnectionAsync(READ)
11-10 09:22:33:888 DEBUG 7512 --- [nio-8080-exec-2] io.lettuce.core.RedisClient              : Trying to get a Redis connection for: RedisURI [host='192.168.115.129', port=7003]
11-10 09:22:33:888 DEBUG 7512 --- [nio-8080-exec-2] io.lettuce.core.RedisClient              : Resolved SocketAddress 192.168.115.129/<unresolved>:7003 using RedisURI [host='192.168.115.129', port=7003]
11-10 09:22:33:888 DEBUG 7512 --- [nio-8080-exec-2] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:7003
11-10 09:22:33:890 DEBUG 7512 --- [nio-8080-exec-2] io.lettuce.core.RedisClient              : Trying to get a Redis connection for: RedisURI [host='192.168.115.129', port=7002]
11-10 09:22:33:892 DEBUG 7512 --- [nio-8080-exec-2] io.lettuce.core.RedisClient              : Resolved SocketAddress 192.168.115.129/<unresolved>:7002 using RedisURI [host='192.168.115.129', port=7002]
11-10 09:22:33:892 DEBUG 7512 --- [nio-8080-exec-2] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:7002
11-10 09:22:33:892 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.protocol.CommandHandler  : [channel=0x8ea4709a, [id: 0x803d93f4] (inactive), chid=0x3d] channelRegistered()
11-10 09:22:33:894 DEBUG 7512 --- [ioEventLoop-4-6] io.lettuce.core.protocol.CommandHandler  : [channel=0x34cd4021, [id: 0x85a1cb96] (inactive), chid=0x3e] channelRegistered()
11-10 09:22:33:898 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.protocol.CommandHandler  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, chid=0x3d] channelActive()
11-10 09:22:33:898 DEBUG 7512 --- [ioEventLoop-4-6] io.lettuce.core.protocol.CommandHandler  : [channel=0x34cd4021, /192.168.115.1:64612 -> /192.168.115.129:7002, chid=0x3e] channelActive()
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-6] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x34cd4021, /192.168.115.1:64612 -> /192.168.115.129:7002, epid=0x1f] activateEndpointAndExecuteBufferedCommands 0 command(s) buffered
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, epid=0x1e] activateEndpointAndExecuteBufferedCommands 0 command(s) buffered
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-6] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x34cd4021, /192.168.115.1:64612 -> /192.168.115.129:7002, epid=0x1f] activating endpoint
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-6] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x34cd4021, /192.168.115.1:64612 -> /192.168.115.129:7002, epid=0x1f] flushCommands()
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, epid=0x1e] activating endpoint
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-6] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x34cd4021, /192.168.115.1:64612 -> /192.168.115.129:7002, epid=0x1f] flushCommands() Flushing 0 commands
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, epid=0x1e] flushCommands()
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, epid=0x1e] flushCommands() Flushing 0 commands
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-6] i.l.core.protocol.ConnectionWatchdog     : [channel=0x34cd4021, /192.168.115.1:64612 -> /192.168.115.129:7002, last known addr=/192.168.115.129:7002] channelActive()
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-6] io.lettuce.core.protocol.CommandHandler  : [channel=0x34cd4021, /192.168.115.1:64612 -> /192.168.115.129:7002, chid=0x3e] channelActive() done
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] i.l.core.protocol.ConnectionWatchdog     : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, last known addr=/192.168.115.129:7003] channelActive()
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.protocol.CommandHandler  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, chid=0x3d] channelActive() done
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-6] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:7002: Success
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:7003: Success
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-6] i.l.core.protocol.ConnectionWatchdog     : [channel=0x34cd4021, /192.168.115.1:64612 -> /192.168.115.129:7002, last known addr=/192.168.115.129:7002] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@63b394dd)
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.RedisChannelHandler      : dispatching command AsyncCommand [type=GET, output=ValueOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, epid=0x1e] write() writeAndFlush command AsyncCommand [type=GET, output=ValueOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:22:33:900 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.protocol.CommandHandler  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, chid=0x3d] write(ctx, AsyncCommand [type=GET, output=ValueOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command], promise)
11-10 09:22:33:902 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.protocol.CommandEncoder  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003] writing command AsyncCommand [type=GET, output=ValueOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:22:33:902 DEBUG 7512 --- [ioEventLoop-4-5] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, epid=0x1e] write() done
11-10 09:22:33:903 DEBUG 7512 --- [ioEventLoop-4-5] i.l.core.protocol.ConnectionWatchdog     : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, last known addr=/192.168.115.129:7003] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@76626038)
11-10 09:22:33:903 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.protocol.CommandHandler  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, chid=0x3d] Received: 10 bytes, 1 commands in the stack
11-10 09:22:33:904 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.protocol.CommandHandler  : [channel=0x8ea4709a, /192.168.115.1:64611 -> /192.168.115.129:7003, chid=0x3d] Stack contains: 1 commands
11-10 09:22:33:904 DEBUG 7512 --- [ioEventLoop-4-5] i.l.core.protocol.RedisStateMachine      : Decode AsyncCommand [type=GET, output=ValueOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:22:33:904 DEBUG 7512 --- [ioEventLoop-4-5] i.l.core.protocol.RedisStateMachine      : Decoded AsyncCommand [type=GET, output=ValueOutput [output=[B@43a98926, error='null'], commandType=io.lettuce.core.protocol.Command], empty stack: true
3.master宕机后，Sentinel会通过相应的规则 将另一台redis升级为master
EBUG 7512 --- [ioEventLoop-4-8] i.l.c.m.MasterSlaveConnectionProvider    : closeStaleConnections() count after expiring: 2
11-10 09:25:31:075 DEBUG 7512 --- [ioEventLoop-4-8] io.lettuce.core.protocol.CommandHandler  : [channel=0x961224db, /192.168.115.1:64679 -> /192.168.115.129:7003, chid=0x48] channelInactive()
11-10 09:25:31:075 DEBUG 7512 --- [ioEventLoop-4-5] io.lettuce.core.protocol.CommandHandler  : [channel=0x7c86c2e2, [id: 0x8447a484] (inactive), chid=0x45] channelUnregistered()
11-10 09:25:31:076 DEBUG 7512 --- [ioEventLoop-4-8] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x961224db, /192.168.115.1:64679 -> /192.168.115.129:7003, epid=0x22] deactivating endpoint handler
11-10 09:25:31:076 DEBUG 7512 --- [ioEventLoop-4-8] io.lettuce.core.protocol.CommandHandler  : [channel=0x961224db, /192.168.115.1:64679 -> /192.168.115.129:7003, chid=0x48] channelInactive() done
11-10 09:25:31:076 DEBUG 7512 --- [ioEventLoop-4-8] i.l.core.protocol.ConnectionWatchdog     : [channel=0x961224db, /192.168.115.1:64679 -> /192.168.115.129:7003, last known addr=/192.168.115.129:7003] channelInactive()
11-10 09:25:31:076 DEBUG 7512 --- [ioEventLoop-4-8] i.l.core.protocol.ConnectionWatchdog     : [channel=0x961224db, /192.168.115.1:64679 -> /192.168.115.129:7003, last known addr=/192.168.115.129:7003] Reconnect scheduling disabled
11-10 09:25:31:076 DEBUG 7512 --- [ioEventLoop-4-8] io.lettuce.core.protocol.CommandHandler  : [channel=0x961224db, /192.168.115.1:64679 -> /192.168.115.129:7003, chid=0x48] channelUnregistered()
11-10 09:25:32:124 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x4585aa47, /192.168.115.1:59804 -> /192.168.115.129:27003, chid=0xa] Received: 123 bytes, 0 commands in the stack
11-10 09:25:32:124 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.RedisStateMachine      : Decode null
11-10 09:25:32:124 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.RedisStateMachine      : Decoded null, empty stack: true
11-10 09:25:32:126 DEBUG 7512 --- [ioEventLoop-4-2] i.l.c.m.SentinelTopologyRefresh          : Received topology changed signal from Redis Sentinel (+sdown), scheduling topology update
11-10 09:25:32:138 DEBUG 7512 --- [ioEventLoop-4-8] io.lettuce.core.protocol.CommandHandler  : [channel=0x9086940e, /192.168.115.1:59805 -> /192.168.115.129:27001, chid=0x8] Received: 123 bytes, 0 commands in the stack
11-10 09:25:32:138 DEBUG 7512 --- [ioEventLoop-4-8] i.l.core.protocol.RedisStateMachine      : Decode null
11-10 09:25:32:138 DEBUG 7512 --- [ioEventLoop-4-8] i.l.core.protocol.RedisStateMachine      : Decoded null, empty stack: true
11-10 09:25:33:152 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x35b4d718, /192.168.115.1:59803 -> /192.168.115.129:27002, chid=0x9] Received: 123 bytes, 0 commands in the stack
11-10 09:25:33:154 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.RedisStateMachine      : Decode null
11-10 09:25:33:154 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.RedisStateMachine      : Decoded null, empty stack: true
11-10 09:25:37:130 DEBUG 7512 --- [xecutorLoop-1-1] i.l.core.masterslave.SentinelConnector   : Refreshing topology
11-10 09:25:37:130 DEBUG 7512 --- [xecutorLoop-1-1] i.l.c.m.SentinelTopologyProvider         : lookup topology for masterId mymaster
11-10 09:25:37:130 DEBUG 7512 --- [xecutorLoop-1-1] io.lettuce.core.RedisClient              : Trying to get a Redis Sentinel connection for one of: [RedisURI [host='192.168.115.129', port=27001], RedisURI [host='192.168.115.129', port=27002], RedisURI [host='192.168.115.129', port=27003]]
11-10 09:25:37:130 DEBUG 7512 --- [xecutorLoop-1-1] io.lettuce.core.RedisClient              : Connecting to Redis Sentinel, address: RedisURI [host='192.168.115.129', port=27001]
11-10 09:25:37:130 DEBUG 7512 --- [xecutorLoop-1-1] io.lettuce.core.RedisClient              : Resolved SocketAddress 192.168.115.129/<unresolved>:27001 using RedisURI [host='192.168.115.129', port=27001]
11-10 09:25:37:130 DEBUG 7512 --- [xecutorLoop-1-1] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:27001
11-10 09:25:37:130 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, [id: 0x518c62a7] (inactive), chid=0x49] channelRegistered()
11-10 09:25:37:130 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] channelActive()
11-10 09:25:37:130 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] activateEndpointAndExecuteBufferedCommands 0 command(s) buffered
11-10 09:25:37:130 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] activating endpoint
11-10 09:25:37:130 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] flushCommands()
11-10 09:25:37:130 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] flushCommands() Flushing 0 commands
11-10 09:25:37:135 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.ConnectionWatchdog     : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, last known addr=/192.168.115.129:27001] channelActive()
11-10 09:25:37:135 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] channelActive() done
11-10 09:25:37:135 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:27001: Success
11-10 09:25:37:135 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisChannelHandler      : dispatching command SubscriptionCommand [type=SENTINEL, output=MapOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:135 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] write() writeAndFlush command SubscriptionCommand [type=SENTINEL, output=MapOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:135 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] write(ctx, SubscriptionCommand [type=SENTINEL, output=MapOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command], promise)
11-10 09:25:37:135 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandEncoder  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001] writing command SubscriptionCommand [type=SENTINEL, output=MapOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:135 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] write() done
11-10 09:25:37:137 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisChannelHandler      : dispatching command SubscriptionCommand [type=SENTINEL, output=ListOfMapsOutput [output=[], error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:137 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] write() writeAndFlush command SubscriptionCommand [type=SENTINEL, output=ListOfMapsOutput [output=[], error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:137 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] write(ctx, SubscriptionCommand [type=SENTINEL, output=ListOfMapsOutput [output=[], error='null'], commandType=io.lettuce.core.protocol.Command], promise)
11-10 09:25:37:137 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandEncoder  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001] writing command SubscriptionCommand [type=SENTINEL, output=ListOfMapsOutput [output=[], error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:137 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] write() done
11-10 09:25:37:137 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.ConnectionWatchdog     : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, last known addr=/192.168.115.129:27001] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@49ae72cd)
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] Received: 617 bytes, 2 commands in the stack
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] Stack contains: 2 commands
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.RedisStateMachine      : Decode SubscriptionCommand [type=SENTINEL, output=MapOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.RedisStateMachine      : Decoded SubscriptionCommand [type=SENTINEL, output=MapOutput [output={name=mymaster, ip=192.168.115.129, port=7002, runid=397a03c41c2672811474c599be00730fae842dd2, flags=master, link-pending-commands=0, link-refcount=1, last-ping-sent=0, last-ok-ping-reply=606, last-ping-reply=606, down-after-milliseconds=5000, info-refresh=10039, role-reported=master, role-reported-time=10057, config-epoch=2, num-slaves=2, num-other-sentinels=2, quorum=2, failover-timeout=60000, parallel-syncs=1}, error='null'], commandType=io.lettuce.core.protocol.Command], empty stack: true
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] Received: 1387 bytes, 1 commands in the stack
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] Stack contains: 1 commands
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.RedisStateMachine      : Decode SubscriptionCommand [type=SENTINEL, output=ListOfMapsOutput [output=[], error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.RedisStateMachine      : Decoded SubscriptionCommand [type=SENTINEL, output=ListOfMapsOutput [output=[{name=192.168.115.129:7001, ip=192.168.115.129, port=7001, runid=, flags=s_down,slave,disconnected, link-pending-commands=3, link-refcount=1, last-ping-sent=10058, last-ok-ping-reply=10058, last-ping-reply=10058, s-down-time=5000, down-after-milliseconds=5000, info-refresh=0, role-reported=slave, role-reported-time=10058, master-link-down-time=0, master-link-status=err, master-host=?, master-port=0, slave-priority=100, slave-repl-offset=0, replica-announced=1}, {name=192.168.115.129:7003, ip=192.168.115.129, port=7003, runid=4358464d40bfd9e8a668899ee80eae940323213e, flags=slave, link-pending-commands=0, link-refcount=1, last-ping-sent=0, last-ok-ping-reply=672, last-ping-reply=672, down-after-milliseconds=5000, info-refresh=8985, role-reported=slave, role-reported-time=10058, master-link-down-time=0, master-link-status=ok, master-host=192.168.115.129, master-port=7002, slave-priority=100, slave-repl-offset=297628, replica-announced=1}], error='null'], commandType=io.lettuce.core.protocol.Command], empty stack: true
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisChannelHandler      : closeAsync()
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] closeAsync()
11-10 09:25:37:138 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisClient              : Trying to get a Redis connection for: RedisURI [host='192.168.115.129', port=7002]
11-10 09:25:37:141 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisClient              : Resolved SocketAddress 192.168.115.129/<unresolved>:7002 using RedisURI [host='192.168.115.129', port=7002]
11-10 09:25:37:141 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:7002
11-10 09:25:37:141 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisClient              : Trying to get a Redis connection for: RedisURI [host='192.168.115.129', port=7003]
11-10 09:25:37:141 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisClient              : Resolved SocketAddress 192.168.115.129/<unresolved>:7003 using RedisURI [host='192.168.115.129', port=7003]
11-10 09:25:37:141 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:7003
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, [id: 0xe93844b8] (inactive), chid=0x4a] channelRegistered()
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] channelInactive()
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, [id: 0x3235ae5a] (inactive), chid=0x4b] channelRegistered()
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-1] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, epid=0x23] deactivating endpoint handler
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] channelInactive() done
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.ConnectionWatchdog     : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, last known addr=/192.168.115.129:27001] channelInactive()
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-1] i.l.core.protocol.ConnectionWatchdog     : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, last known addr=/192.168.115.129:27001] Reconnect scheduling disabled
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-1] io.lettuce.core.protocol.CommandHandler  : [channel=0x340a0472, /192.168.115.1:64683 -> /192.168.115.129:27001, chid=0x49] channelUnregistered()
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] channelActive()
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] activateEndpointAndExecuteBufferedCommands 0 command(s) buffered
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] activating endpoint
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] flushCommands()
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] flushCommands() Flushing 0 commands
11-10 09:25:37:142 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.ConnectionWatchdog     : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, last known addr=/192.168.115.129:7002] channelActive()
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] channelActive() done
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:7002: Success
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] channelActive()
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.RedisChannelHandler      : dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] activateEndpointAndExecuteBufferedCommands 0 command(s) buffered
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] activating endpoint
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] write() writeAndFlush command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] flushCommands()
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] flushCommands() Flushing 0 commands
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] write(ctx, AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command], promise)
11-10 09:25:37:145 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.ConnectionWatchdog     : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, last known addr=/192.168.115.129:7003] channelActive()
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] channelActive() done
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.RedisClient              : Connecting to Redis at 192.168.115.129/<unresolved>:7003: Success
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandEncoder  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002] writing command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.RedisChannelHandler      : dispatching command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] write() writeAndFlush command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] write(ctx, AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command], promise)
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] write() done
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.ConnectionWatchdog     : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, last known addr=/192.168.115.129:7002] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@148f3635)
11-10 09:25:37:146 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandEncoder  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003] writing command AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] write() done
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.RedisChannelHandler      : dispatching command TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] write() writeAndFlush command TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] write() done
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] write(ctx, TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command], promise)
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.RedisChannelHandler      : dispatching command TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] write() writeAndFlush command TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] write(ctx, TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command], promise)
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandEncoder  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002] writing command TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandEncoder  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003] writing command TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] write() done
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] Received: 5 bytes, 2 commands in the stack
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] Stack contains: 2 commands
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.RedisStateMachine      : Decode AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.ConnectionWatchdog     : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, last known addr=/192.168.115.129:7003] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@1428ff18)
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.RedisStateMachine      : Decoded AsyncCommand [type=CLIENT, output=StatusOutput [output=OK, error='null'], commandType=io.lettuce.core.protocol.Command], empty stack: true
11-10 09:25:37:148 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] Received: 5 bytes, 2 commands in the stack
11-10 09:25:37:152 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] Stack contains: 2 commands
11-10 09:25:37:152 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.RedisStateMachine      : Decode AsyncCommand [type=CLIENT, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:152 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.RedisStateMachine      : Decoded AsyncCommand [type=CLIENT, output=StatusOutput [output=OK, error='null'], commandType=io.lettuce.core.protocol.Command], empty stack: true
11-10 09:25:37:154 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] Received: 11 bytes, 1 commands in the stack
11-10 09:25:37:154 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] Stack contains: 1 commands
11-10 09:25:37:154 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] Received: 11 bytes, 1 commands in the stack
11-10 09:25:37:154 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.RedisStateMachine      : Decode TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:154 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] Stack contains: 1 commands
11-10 09:25:37:154 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.RedisStateMachine      : Decoded TimedAsyncCommand [type=PING, output=StatusOutput [output=NODES, error='null'], commandType=io.lettuce.core.protocol.Command], empty stack: true
11-10 09:25:37:154 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.RedisStateMachine      : Decode TimedAsyncCommand [type=PING, output=StatusOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command]
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.RedisStateMachine      : Decoded TimedAsyncCommand [type=PING, output=StatusOutput [output=NODES, error='null'], commandType=io.lettuce.core.protocol.Command], empty stack: true
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.RedisChannelHandler      : closeAsync()
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] closeAsync()
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.RedisChannelHandler      : closeAsync()
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] closeAsync()
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] channelInactive()
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.masterslave.SentinelConnector   : New topology: [RedisMasterSlaveNode [redisURI=RedisURI [host='192.168.115.129', port=7003], role=SLAVE], RedisMasterSlaveNode [redisURI=RedisURI [host='192.168.115.129', port=7002], role=MASTER]]
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-3] i.l.c.m.MasterSlaveConnectionProvider    : closeStaleConnections() count before expiring: 2
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-2] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, epid=0x24] deactivating endpoint handler
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-3] i.l.c.m.MasterSlaveConnectionProvider    : closeStaleConnections() count after expiring: 2
11-10 09:25:37:155 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] channelInactive() done
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.ConnectionWatchdog     : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, last known addr=/192.168.115.129:7002] channelInactive()
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] channelInactive()
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-2] i.l.core.protocol.ConnectionWatchdog     : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, last known addr=/192.168.115.129:7002] Reconnect scheduling disabled
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-2] io.lettuce.core.protocol.CommandHandler  : [channel=0x28e9188c, /192.168.115.1:64684 -> /192.168.115.129:7002, chid=0x4a] channelUnregistered()
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-3] i.lettuce.core.protocol.DefaultEndpoint  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, epid=0x25] deactivating endpoint handler
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] channelInactive() done
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.ConnectionWatchdog     : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, last known addr=/192.168.115.129:7003] channelInactive()
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-3] i.l.core.protocol.ConnectionWatchdog     : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, last known addr=/192.168.115.129:7003] Reconnect scheduling disabled
11-10 09:25:37:158 DEBUG 7512 --- [ioEventLoop-4-3] io.lettuce.core.protocol.CommandHandler  : [channel=0x6cf9a927, /192.168.115.1:64685 -> /192.168.115.129:7003, chid=0x4b] channelUnregistered()

设置键值

在这里插入图片描述
查看键值
在这里插入图片描述

丢爸
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
SSM整合SpringSession造成的每一分钟刷一次redis-lettuce日志问题
byteRun的博客
12-22 1065
问题：每分钟刷一次 2020-12-04 16:23:00[pool-55-thread-1hread][DEBUG]( io.netty.util.internal.logging.Slf4JLogger.debug(Slf4JLogger.java:81)) [/127.0.0.1:45030 -> /127.0.0.1:6379] write() writeAndFlush Command Command [type=SMEMBERS, output=ValueSetOutput [outp
linux-redis绿色版（推荐）
01-07
Linux下的Redis是一个高效、开源的键值存储系统，常用于数据缓存、消息队列以及数据库等场景。Redis因其出色的速度和丰富的数据结构支持而备受青睐。本资源为"linux-redis绿色版"，适用于在Linux环境中快速部署Redis...
springboot之使用redis为mybatis二级缓存
lss0555的博客
01-28 790
一.前言 Mybatis默认开启一级缓存,二级缓存需要手动开启。Mybatis的二级缓存是多个SqlSession共享的，作用于是mapper配置文件中同一个namespace，不同的SqlSession两次执行相同namespace下的sql语句且参数如果也一样，则通过缓存查询的cacheKey也是一样的,则最终执行的sql语句是相同的。每次查询都会先看看缓存中是否有对应查询结果，如果有就从缓存...
11. linux环境redis哨兵模式的搭建
hznb_369的博客
03-28 904
主从复制
springboot+redis主从复制、哨兵、读写分离
Remember_Z的博客
03-02 6138
redis安装、主从配置、哨兵配置、以及在springboot中的集成、读写分离等。
linux下的redis使用及redis集群（主从、哨兵）
qq_43050847的博客
09-07 1520
文章目录linux下安装redisredis集群Redis主从复制的搭建（一主二仆）角色设计redis主库搭建redis从库搭建测试主从复制的机制Redis主从复制（一主两从/一主多从）的分析Redis Sentinel（高可用集群-哨兵模式）配置Sentinel.conf文件启动reids集群启动sentinel测试 linux下安装redis 上传文件到opt文件夹 tar zxvf redis-3.2.9.tar.gz 解压 mv redis-3.2.9 /usr/local/ 移动redis文件夹
linux搭建redis哨兵模式.rar
03-20
总结，Linux环境下搭建Redis哨兵模式涉及多个步骤，包括环境准备、Redis和Sentinel的安装与配置，以及哨兵集群的搭建与测试。这个过程旨在确保Redis服务在面临单点故障时，仍能保持高可用性和数据一致性，对于构建...
tomcat-redis依赖jar包
08-17
- Redis集群：当单个Redis实例无法满足需求时，可以考虑使用Redis Cluster或哨兵（Sentinel）系统实现数据分片和高可用性。 - Spring Data Redis：如果使用Spring框架，可以借助Spring Data Redis模块简化Redis的...
redis-session-manager-redis-session-manager-2.0.8.tar.gz
06-02
2. **高可用性**：Redis可以通过复制和哨兵模式提供高可用性，确保服务不中断。 3. **性能优化**：由于Redis是内存数据库，因此读写速度极快，对会话操作响应迅速。 4. **数据持久化**：通过AOF（Append Only File）...
redis哨兵模式搭建.rar
07-13
Redis Sentinel是Redis的一个高可用性解决方案，用于监控、故障检测以及自动故障恢复主从集群。在Redis中， Sentinel系统可以确保即使在主服务器宕机的情况下，数据仍然能够被正确访问，通过将流量重新路由到备用...
Redis集群-Redis安装、Redis主从复制、哨兵、Redis集群
12-25
在实际的企业环境中，我们通常使用Linux环境来安装和部署Redis。 二、主从复制 主从复制是Redis集群中的一种重要技术，它可以避免Redis单点故障，实现读写分离架构，满足读多写少的应用场景。我们可以通过在redis....
Another-Redis-Desktop-Manager Redis客户端
05-15
- **使用哨兵或集群**：在高可用性需求下，使用哨兵系统或Redis Cluster来实现故障转移。 总之，Another-Redis-Desktop-Manager作为一款实用的Redis客户端，使得对Redis数据库的管理变得更加简单和直观，对于开发...
Linux学习教程之redis哨兵集群详解
01-20
Sentinel(哨兵)是用于监控redis集群中Master状态的工具，其已经被集成在redis2.4+的版本中，下面话不多说了，来一起看看详细的介绍吧 1、Sentinel 哨兵 Sentinel（哨兵）是Redis 的高可用性解决方案：由一个或多个...
Redis哨兵主从模式+keepalived.docx
12-12
"Redis哨兵主从模式+keepalived" Redis哨兵主从模式是指 Redis 的一种高可用性解决方案，通过哨兵模式实现自动故障切换和虚拟IP漂移，以提供高可用性的Redis服务。下面是相关知识点的详细解释： 一、Redis主从复制...
redis-linux版本
最新发布
06-26
在实际生产环境中，你可能需要配置Redis以实现持久化（RDB或AOF）、主从复制、哨兵系统（Sentinel）和集群（Cluster）等高级功能。`redis.conf`配置文件中提供了相应的选项，可以根据`readme.txt`中的指南进行设置。...
Sprintboot 2.3.1链接redis，链接redis 127.0.0.1错误异常查找
zzhongcy的专栏
08-05 1080
介绍 以前使用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 lib..
Linux下安装配置redis详细教程，并配置哨兵模式，redis中文详解
kzhzhang的专栏
07-02 1349
Linux下安装配置redis详细教程，并配置哨兵模式。 Redis配置文件中文详解。
Redis哨兵模式（一主二从三哨兵）
热门推荐
weixin_38568503的博客
04-25 2万+
目录环境：安装redis:使用Redis主从复制的作用：配置redis一主二从：redis启动前的准备工作：配置redis三哨兵： 环境： 环境：redis6.2.6 linux虚拟机一台，contos7的 一主两从三哨兵集群，当master节点宕机时，通过哨兵(sentinel)重新推选出新的master节点，保证集群的可用性。 哨兵的主要功能： 1.集群监控：负责监控 Redis master 和 slave 进程是否正常工作。 2.消息通知：如果某个 Redis 实例有故障，那么哨兵负责发送消息
linux中配置redis主从复制及开启哨兵模式
welcome
12-24 460
将原来的配置文件复制到文件夹，该backendservice配置文件本来没有的，具体见上一篇文章。启动三个redis服务，一会6379作为主节点，6380和6381作为从节点。此时回到6379主节点，查看其主从复制相关信息，拥有两个从节点。开多两个窗口，一个访问6380，一个访问6381。再次查看主从复制的相关信息，发现它们已变为从节点。按esc，输入“:wq”保存并退出。按esc，输入“:wq”保存并退出。按esc，输入“:wq”保存并退出。按esc，输入“:wq”保存并退出。
linux 怎么配置redis哨兵模式
09-23
要配置Redis哨兵模式，您需要进行以下步骤： 1. 首先，确保您已经安装了Redis。您可以通过运行以下命令来检查Redis的安装情况： ``` redis-server --version ``` 2. 确保您已经在主节点和所有的哨兵节点上正确配置了Redis。您可以使用编辑器打开Redis配置文件（通常位于`/etc/redis/redis.conf`），然后进行相应的配置。以下是您需要注意的一些配置项： - `port`：指定Redis实例的端口号。 - `bind`：指定Redis实例绑定的IP地址。 - `daemonize`：将其设置为`yes`以在后台运行Redis。 - `logfile`：指定将日志写入的文件路径。 - `dir`：指定Redis实例的工作目录。 3. 在主节点上，将`sentinel monitor`配置项添加到Redis配置文件中。这将告诉哨兵实例要监视的主节点的名称、IP地址和端口号。例如： ``` sentinel monitor mymaster 127.0.0.1 6379 2 ``` 4. 在每个哨兵节点上，将`sentinel config-redis`配置项添加到Redis配置文件中。这将告诉哨兵实例如何连接到主节点和其他哨兵节点。例如： ``` sentinel config-redis mymaster 127.0.0.1 6379 2 ``` 5. 启动所有的Redis实例和哨兵实例。您可以使用以下命令启动Redis和哨兵： ``` redis-server /path/to/redis.conf redis-sentinel /path/to/sentinel.conf ``` 6. 您可以使用`redis-cli`命令连接到哨兵节点，并检查哨兵模式的状态。例如，运行以下命令以连接到哨兵节点： ``` redis-cli -h 127.0.0.1 -p 26379 ``` 以上是配置Redis哨兵模式的基本步骤。根据您的需求，您可能还需要进行其他配置更改。请确保您在开始配置之前备份Redis配置文件。

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值