redis 主从复制下

最新推荐文章于 2024-12-10 15:55:14 发布
最新推荐文章于 2024-12-10 15:55:14 发布
阅读量264 收藏
点赞数
分类专栏： redis 文章标签： redis
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/ZhuxiaowenLinda/article/details/105151986
版权
该博客详细记录了在 CentOS7 系统中配置 Redis 主从复制的过程，包括启动 Redis 服务器、编辑配置文件、监控 sentinel 等步骤，并展示了通过命令行工具进行主从切换及验证数据同步的实践操作。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

Connecting to 192.168.159.12:22...
Connection established.
To escape to local shell, press 'Ctrl+Alt+]'.

Last login: Fri Mar 27 11:08:13 2020 from 192.168.159.1
[root@centos7002 ~]# cd /myredis/
[root@centos7002 myredis]# ls -l
总用量 388
-rw-r--r-- 1 root root   496 3月  27 11:04 6379.log
-rw-r--r-- 1 root root 61810 3月  27 10:18 redis6379.conf
-rw-r--r-- 1 root root 61810 3月  27 10:48 redis6380.conf
-rw-r--r-- 1 root root 61810 3月  27 11:01 redis6381.conf
-rw-r--r-- 1 root root 61799 3月  25 19:06 redis_aof.conf
-rw-r--r-- 1 root root 61798 3月  23 11:35 redis.conf
-rw-r--r-- 1 root root 61797 3月  10 15:04 redis-init.conf
[root@centos7002 myredis]# vi redis6379.conf 
[root@centos7002 myredis]# cd /usr/local/bin/
[root@centos7002 bin]# ls -l
总用量 32748
-rw-r--r-- 1 root root    2496 3月  27 11:07 6380.log
-rw-r--r-- 1 root root    1187 3月  26 13:16 appendonly.aof
-rw-r--r-- 1 root root     149 3月  26 13:25 dump.rdb
-rwxr-xr-x 1 root root 4366608 3月  10 14:20 redis-benchmark
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-check-aof
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-check-rdb
-rwxr-xr-x 1 root root 4806832 3月  10 14:20 redis-cli
lrwxrwxrwx 1 root root      12 3月  10 14:20 redis-sentinel -> redis-server
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-server
[root@centos7002 bin]# cd /myredis/
[root@centos7002 myredis]# ls -l
总用量 388
-rw-r--r-- 1 root root   496 3月  27 11:04 6379.log
-rw-r--r-- 1 root root 61810 3月  27 10:18 redis6379.conf
-rw-r--r-- 1 root root 61810 3月  27 10:48 redis6380.conf
-rw-r--r-- 1 root root 61810 3月  27 11:01 redis6381.conf
-rw-r--r-- 1 root root 61799 3月  25 19:06 redis_aof.conf
-rw-r--r-- 1 root root 61798 3月  23 11:35 redis.conf
-rw-r--r-- 1 root root 61797 3月  10 15:04 redis-init.conf
[root@centos7002 myredis]# vi redis6379.conf 
[root@centos7002 myredis]# vi redis6380.conf 
[root@centos7002 myredis]# vi redis6381.conf 
[root@centos7002 myredis]# cd /usr/local/bin/
[root@centos7002 bin]# ls -l
总用量 32748
-rw-r--r-- 1 root root    2496 3月  27 11:07 6380.log
-rw-r--r-- 1 root root    1187 3月  26 13:16 appendonly.aof
-rw-r--r-- 1 root root     149 3月  26 13:25 dump.rdb
-rwxr-xr-x 1 root root 4366608 3月  10 14:20 redis-benchmark
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-check-aof
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-check-rdb
-rwxr-xr-x 1 root root 4806832 3月  10 14:20 redis-cli
lrwxrwxrwx 1 root root      12 3月  10 14:20 redis-sentinel -> redis-server
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-server
[root@centos7002 bin]# vi 6380.log
[root@centos7002 bin]# ps -ef|grep redis
root     17104 13811  0 11:04 pts/4    00:00:00 redis-cli -p 6379
root     17248     1  0 11:07 ?        00:00:01 redis-server 127.0.0.1:6380
root     17292 16996  0 11:07 pts/1    00:00:00 redis-cli -p 6380
root     17390     1  0 11:08 ?        00:00:01 redis-server 127.0.0.1:6381
root     17407 17320  0 11:08 pts/2    00:00:00 redis-cli -p 6381
root     18212 17518  0 11:20 pts/0    00:00:00 grep --color=auto redis
root     27169     1  0 3月26 ?       00:01:57 redis-server 127.0.0.1:6379
[root@centos7002 bin]# cd /myredis/
[root@centos7002 myredis]# ls -l
总用量 388
-rw-r--r-- 1 root root   496 3月  27 11:04 6379.log
-rw-r--r-- 1 root root 61810 3月  27 10:18 redis6379.conf
-rw-r--r-- 1 root root 61810 3月  27 10:48 redis6380.conf
-rw-r--r-- 1 root root 61810 3月  27 11:01 redis6381.conf
-rw-r--r-- 1 root root 61799 3月  25 19:06 redis_aof.conf
-rw-r--r-- 1 root root 61798 3月  23 11:35 redis.conf
-rw-r--r-- 1 root root 61797 3月  10 15:04 redis-init.conf
[root@centos7002 myredis]# touch sentinel.conf
[root@centos7002 myredis]# ls -l
总用量 388
-rw-r--r-- 1 root root   496 3月  27 11:04 6379.log
-rw-r--r-- 1 root root 61810 3月  27 10:18 redis6379.conf
-rw-r--r-- 1 root root 61810 3月  27 10:48 redis6380.conf
-rw-r--r-- 1 root root 61810 3月  27 11:01 redis6381.conf
-rw-r--r-- 1 root root 61799 3月  25 19:06 redis_aof.conf
-rw-r--r-- 1 root root 61798 3月  23 11:35 redis.conf
-rw-r--r-- 1 root root 61797 3月  10 15:04 redis-init.conf
-rw-r--r-- 1 root root     0 3月  27 21:52 sentinel.conf
[root@centos7002 myredis]# vi sentinel.conf 
[root@centos7002 myredis]# cd /usr/local/bin/
[root@centos7002 bin]# ls -l
总用量 33788
-rw-r--r-- 1 root root    6339 3月  27 21:15 6379.log
-rw-r--r-- 1 root root  351127 3月  27 22:08 6380.log
-rw-r--r-- 1 root root  367097 3月  27 22:08 6381.log
-rw-r--r-- 1 root root    1245 3月  27 13:04 appendonly.aof
-rw-r--r-- 1 root root     204 3月  27 21:15 dump6379.rdb
-rw-r--r-- 1 root root     211 3月  27 21:16 dump6380.rdb
-rw-r--r-- 1 root root     211 3月  27 21:17 dump6981.rdb
-rw-r--r-- 1 root root     247 3月  27 13:11 dump.rdb
-rwxr-xr-x 1 root root 4366608 3月  10 14:20 redis-benchmark
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-check-aof
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-check-rdb
-rwxr-xr-x 1 root root 4806832 3月  10 14:20 redis-cli
lrwxrwxrwx 1 root root      12 3月  10 14:20 redis-sentinel -> redis-server
-rwxr-xr-x 1 root root 8111816 3月  10 14:20 redis-server
[root@centos7002 bin]# redis-sentinel /myredis/sentinel.conf 
23537:X 27 Mar 2020 22:09:41.064 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
23537:X 27 Mar 2020 22:09:41.064 # Redis version=5.0.5, bits=64, commit=00000000, modified=0, pid=23537, just started
23537:X 27 Mar 2020 22:09:41.064 # Configuration loaded
23537:X 27 Mar 2020 22:09:41.066 * Increased maximum number of open files to 10032 (it was originally set to 1024).
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 5.0.5 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in sentinel mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 26379
 |    `-._   `._    /     _.-'    |     PID: 23537
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

23537:X 27 Mar 2020 22:09:41.068 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
23537:X 27 Mar 2020 22:09:41.071 # Sentinel ID is 4da79d249dfab70d50f5eb97d2655a6a52264234
23537:X 27 Mar 2020 22:09:41.071 # +monitor master host6379 127.0.0.1 6379 quorum 1
23537:X 27 Mar 2020 22:10:11.130 # +sdown master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:10:11.130 # +odown master host6379 127.0.0.1 6379 #quorum 1/1
23537:X 27 Mar 2020 22:10:11.130 # +new-epoch 1
23537:X 27 Mar 2020 22:10:11.130 # +try-failover master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:10:11.134 # +vote-for-leader 4da79d249dfab70d50f5eb97d2655a6a52264234 1
23537:X 27 Mar 2020 22:10:11.134 # +elected-leader master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:10:11.134 # +failover-state-select-slave master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:10:11.206 # -failover-abort-no-good-slave master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:10:11.262 # Next failover delay: I will not start a failover before Fri Mar 27 22:16:11 2020
23537:X 27 Mar 2020 22:10:20.599 * +slave slave 127.0.0.1:6381 127.0.0.1 6381 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:10:20.650 # -sdown master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:10:20.650 # -odown master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:10:30.610 * +slave slave 127.0.0.1:6380 127.0.0.1 6380 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:12:01.349 # +sdown master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:12:01.349 # +odown master host6379 127.0.0.1 6379 #quorum 1/1
23537:X 27 Mar 2020 22:16:11.319 # +new-epoch 2
23537:X 27 Mar 2020 22:16:11.319 # +try-failover master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:11.327 # +vote-for-leader 4da79d249dfab70d50f5eb97d2655a6a52264234 2
23537:X 27 Mar 2020 22:16:11.327 # +elected-leader master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:11.327 # +failover-state-select-slave master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:11.410 # +selected-slave slave 127.0.0.1:6381 127.0.0.1 6381 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:11.411 * +failover-state-send-slaveof-noone slave 127.0.0.1:6381 127.0.0.1 6381 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:11.478 * +failover-state-wait-promotion slave 127.0.0.1:6381 127.0.0.1 6381 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:12.291 # +promoted-slave slave 127.0.0.1:6381 127.0.0.1 6381 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:12.291 # +failover-state-reconf-slaves master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:12.342 * +slave-reconf-sent slave 127.0.0.1:6380 127.0.0.1 6380 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:13.316 * +slave-reconf-inprog slave 127.0.0.1:6380 127.0.0.1 6380 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:13.316 * +slave-reconf-done slave 127.0.0.1:6380 127.0.0.1 6380 @ host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:13.377 # +failover-end master host6379 127.0.0.1 6379
23537:X 27 Mar 2020 22:16:13.378 # +switch-master host6379 127.0.0.1 6379 127.0.0.1 6381
23537:X 27 Mar 2020 22:16:13.378 * +slave slave 127.0.0.1:6380 127.0.0.1 6380 @ host6379 127.0.0.1 6381
23537:X 27 Mar 2020 22:16:13.378 * +slave slave 127.0.0.1:6379 127.0.0.1 6379 @ host6379 127.0.0.1 6381
23537:X 27 Mar 2020 22:16:43.380 # +sdown slave 127.0.0.1:6379 127.0.0.1 6379 @ host6379 127.0.0.1 6381
23537:X 27 Mar 2020 22:19:45.342 # -sdown slave 127.0.0.1:6379 127.0.0.1 6379 @ host6379 127.0.0.1 6381
23537:X 27 Mar 2020 22:19:55.343 * +convert-to-slave slave 127.0.0.1:6379 127.0.0.1 6379 @ host6379 127.0.0.1 6381
 

127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:2
slave0:ip=127.0.0.1,port=6381,state=online,offset=3624,lag=1
slave1:ip=127.0.0.1,port=6380,state=online,offset=3624,lag=1
master_replid:037f5877f0fadb01713e95b1e4317b385c0e3c4b
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3624
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:3624
127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:1
slave0:ip=127.0.0.1,port=6380,state=online,offset=3792,lag=1
master_replid:037f5877f0fadb01713e95b1e4317b385c0e3c4b
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3792
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:3792
127.0.0.1:6379> keys *
1) "k2"
2) "k3"
3) "k1"
127.0.0.1:6379> shutdown
not connected> exit
[root@centos7002 bin]# 
[root@centos7002 bin]# redis-server /myredis/redis6379.conf 
[root@centos7002 bin]# redis-cli -p 6379
127.0.0.1:6379> keys *
1) "k2"
2) "k1"
3) "k3"
127.0.0.1:6379> shutdown
not connected> exit
[root@centos7002 bin]# redis-server /myredis/redis6379.conf 
[root@centos7002 bin]# redis-cli -p 6379
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6381
master_link_status:up
master_last_io_seconds_ago:1
master_sync_in_progress:0
slave_repl_offset:20757
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:331adbbf176584d69e67dd3a717d45cc76a0362f
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:20757
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:19776
repl_backlog_histlen:982
127.0.0.1:6379> get k4
"v4"
127.0.0.1:6379> 
 

Connecting to 192.168.159.12:22...
Connection established.
To escape to local shell, press 'Ctrl+Alt+]'.

Last login: Fri Mar 27 10:09:37 2020 from 192.168.159.1
[root@centos7002 ~]# cd /usr/local/bin/
[root@centos7002 bin]# redis-server /myredis/redis6380.conf 
[root@centos7002 bin]# redis-cli -p 6380
127.0.0.1:6380> ping
PONG
127.0.0.1:6380> keys *
(empty list or set)
127.0.0.1:6380> info replication
# Replication
role:master
connected_slaves:0
master_replid:4f2bcd59d0657f70196cee2aeca8b52c17599d5c
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:0
second_repl_offset:-1
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
127.0.0.1:6380> slaveof 127.0.0.1 6379
OK
127.0.0.1:6380> get k6
"v6"
127.0.0.1:6380> get k1
"v1"
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:up
master_last_io_seconds_ago:8
master_sync_in_progress:0
slave_repl_offset:304
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:94ef8e60e3a65d8725fbe19c3bee14d61c9f747e
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:304
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:29
repl_backlog_histlen:276
127.0.0.1:6380> set k7 v77
(error) READONLY You can't write against a read only replica.
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:1145
master_link_down_since_seconds:13
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:94ef8e60e3a65d8725fbe19c3bee14d61c9f747e
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:1145
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:29
repl_backlog_histlen:1117
127.0.0.1:6380> keys *
(empty list or set)
127.0.0.1:6380> get k1
"v1"
127.0.0.1:6380> keys *
1) "k1"
127.0.0.1:6380> shutdown
not connected> exit
[root@centos7002 bin]# redis-server /myredis/redis6380.conf 
[root@centos7002 bin]# redis-cli -p 6380
127.0.0.1:6380> ping
PONG
127.0.0.1:6380> keys *
1) "k1"
127.0.0.1:6380> shutdown
not connected> exit
[root@centos7002 bin]# redis-server /myredis/redis6380.conf 
[root@centos7002 bin]# redis-cli -p 6380
127.0.0.1:6380> keys *
1) "k1"
127.0.0.1:6380> info replication
# Replication
role:master
connected_slaves:0
master_replid:b22af0635dddf1e61fb28816cec7e10835f5072e
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:0
second_repl_offset:-1
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
127.0.0.1:6380> get k2
(nil)
127.0.0.1:6380> slaveof 127.0.0.1 6379
OK
127.0.0.1:6380> keys *
1) "k2"
2) "k1"
3) "k3"
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:up
master_last_io_seconds_ago:8
master_sync_in_progress:0
slave_repl_offset:3820
slave_priority:100
slave_read_only:1
connected_slaves:1
slave0:ip=127.0.0.1,port=6381,state=online,offset=3820,lag=1
master_replid:037f5877f0fadb01713e95b1e4317b385c0e3c4b
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3820
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:3051
repl_backlog_histlen:770
127.0.0.1:6380> keys *
1) "k2"
2) "k1"
3) "k3"
127.0.0.1:6380> slaveof no one
OK
127.0.0.1:6380> set k4
(error) ERR wrong number of arguments for 'set' command
127.0.0.1:6380> set k4 v4
OK
127.0.0.1:6380> slaveof 127.0.0.1 6379
OK
127.0.0.1:6380> keys *
1) "k2"
2) "k3"
3) "k1"
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:4785
master_link_down_since_seconds:35
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:bc2946f129f223f9790e6482c323302f4db9c112
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:4785
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:157
repl_backlog_histlen:4629
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:4785
master_link_down_since_seconds:149
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:bc2946f129f223f9790e6482c323302f4db9c112
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:4785
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:157
repl_backlog_histlen:4629
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:4785
master_link_down_since_seconds:196
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:bc2946f129f223f9790e6482c323302f4db9c112
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:4785
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:157
repl_backlog_histlen:4629
127.0.0.1:6380> keys *
1) "k2"
2) "k3"
3) "k1"
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:4785
master_link_down_since_seconds:237
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:bc2946f129f223f9790e6482c323302f4db9c112
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:4785
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:157
repl_backlog_histlen:4629
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6381
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:13502
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:331adbbf176584d69e67dd3a717d45cc76a0362f
master_replid2:bc2946f129f223f9790e6482c323302f4db9c112
master_repl_offset:13502
second_repl_offset:4786
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:157
repl_backlog_histlen:13346
127.0.0.1:6380> get k4
"v4"
127.0.0.1:6380> 
 

Connecting to 192.168.159.12:22...
Connection established.
To escape to local shell, press 'Ctrl+Alt+]'.

Last login: Fri Mar 27 11:03:32 2020 from 192.168.159.1
[root@centos7002 ~]# redis-server /myredis/redis6381.conf 
[root@centos7002 ~]# redis-cli -p 6381
127.0.0.1:6381> ping
PONG
127.0.0.1:6381> keys *
(empty list or set)
127.0.0.1:6381> info replication
# Replication
role:master
connected_slaves:0
master_replid:949a8c6dd2d1a5b588d7173d4b5e64b5e6de70ad
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:0
second_repl_offset:-1
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
127.0.0.1:6381> SLAVEOF 127.0.0.1 6379
OK
127.0.0.1:6381> get k4
"v4"
127.0.0.1:6381> get k2
"22"
127.0.0.1:6381> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:up
master_last_io_seconds_ago:10
master_sync_in_progress:0
slave_repl_offset:332
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:94ef8e60e3a65d8725fbe19c3bee14d61c9f747e
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:332
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:332
127.0.0.1:6381> set k7 v777
(error) READONLY You can't write against a read only replica.
127.0.0.1:6381> keys *
1) "k4"
2) "debt"
3) "balance"
4) "k5"
5) "k6"
6) "k2"
7) "k3"
8) "k1"
9) "k7"
127.0.0.1:6381> shutdown
not connected> exit
[root@centos7002 ~]# redis-cli -p 6381
Could not connect to Redis at 127.0.0.1:6381: Connection refused
not connected> exit
[root@centos7002 ~]# cd /usr/local/bin/
[root@centos7002 bin]# redis-server /myredis/redis6381.conf 
[root@centos7002 bin]# redis-cli -p 6381
127.0.0.1:6381> ping
PONG
127.0.0.1:6381> keys *
(empty list or set)
127.0.0.1:6381> info replication
# Replication
role:master
connected_slaves:0
master_replid:189d3cfceee3e0125907259f4f2f4d77da11126e
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:0
second_repl_offset:-1
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
127.0.0.1:6381> SLAVEOF 127.0.0.1 6381
OK
127.0.0.1:6381> keys *
(empty list or set)
127.0.0.1:6381> SLAVEOF 127.0.0.1 6379
OK
127.0.0.1:6381> keys *
1) "k4"
2) "k3"
3) "k2"
4) "k1"
5) "debt"
6) "k6"
7) "balance"
8) "k5"
9) "k7"
127.0.0.1:6381> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:up
master_last_io_seconds_ago:10
master_sync_in_progress:0
slave_repl_offset:935
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:94ef8e60e3a65d8725fbe19c3bee14d61c9f747e
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:935
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:880
repl_backlog_histlen:56
127.0.0.1:6381> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:1145
master_link_down_since_seconds:26
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:94ef8e60e3a65d8725fbe19c3bee14d61c9f747e
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:1145
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:880
repl_backlog_histlen:266
127.0.0.1:6381> keys *
1) "k4"
2) "k3"
3) "k2"
4) "k1"
5) "debt"
6) "k6"
7) "balance"
8) "k5"
9) "k7"
127.0.0.1:6381> get k1
"v1"
127.0.0.1:6381> keys *
1) "k1"
127.0.0.1:6381> get k2
"v2"
127.0.0.1:6381> get k3
"v3"
127.0.0.1:6381> slaveof 127.0.0.1 6380
OK
127.0.0.1:6381> slaveof 127.0.0.1 6379
OK
127.0.0.1:6381> slaveof 127.0.0.1 6380
OK
127.0.0.1:6381> keys *
1) "k2"
2) "k1"
3) "k4"
4) "k3"
127.0.0.1:6381> get k4
"v4"
127.0.0.1:6381> slaveof 127.0.0.1 6379
OK
127.0.0.1:6381> keys *
1) "k2"
2) "k1"
3) "k3"
127.0.0.1:6381> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:4785
master_link_down_since_seconds:44
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:bc2946f129f223f9790e6482c323302f4db9c112
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:4785
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:4785
127.0.0.1:6381> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:4785
master_link_down_since_seconds:145
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:bc2946f129f223f9790e6482c323302f4db9c112
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:4785
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:4785
127.0.0.1:6381> keys *
1) "k2"
2) "k1"
3) "k3"
127.0.0.1:6381> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
master_sync_in_progress:0
slave_repl_offset:4785
master_link_down_since_seconds:261
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:bc2946f129f223f9790e6482c323302f4db9c112
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:4785
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:4785
127.0.0.1:6381> info replication
# Replication
role:master
connected_slaves:1
slave0:ip=127.0.0.1,port=6380,state=online,offset=13768,lag=1
master_replid:331adbbf176584d69e67dd3a717d45cc76a0362f
master_replid2:bc2946f129f223f9790e6482c323302f4db9c112
master_repl_offset:13768
second_repl_offset:4786
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:13768
127.0.0.1:6381> keys *
1) "k2"
2) "k1"
3) "k3"
127.0.0.1:6381> set k4 v4
OK
127.0.0.1:6381> get k4
"v4"
127.0.0.1:6381> info replication
# Replication
role:master
connected_slaves:2
slave0:ip=127.0.0.1,port=6380,state=online,offset=26322,lag=1
slave1:ip=127.0.0.1,port=6379,state=online,offset=26322,lag=1
master_replid:331adbbf176584d69e67dd3a717d45cc76a0362f
master_replid2:bc2946f129f223f9790e6482c323302f4db9c112
master_repl_offset:26322
second_repl_offset:4786
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:26322
127.0.0.1:6381> 
 

第02篇：Redis主从复制getshell1
08-03
1、生成恶意.so文件，下载RedisModules-ExecuteCommand使用make编译即可生成 1、监听本地1234端口 2、将Redis服务器设置
Redis主从复制问题和扩容问题的解决思路
01-19
为了解决Redis主从Copy的问题，有如下两个解决方案： 主动复制所谓主动复制，就是业务层双写多个Redis，避开Redis自带的主从复制。但是自己干同步，就会产生一致性问题，为了保证主从一致，需要加入一系列的验证机制...
Redis拒绝连接：Could not connect to Redis at 127.0.0.1:6379: Connection refused
qq_41863065的博客
10-31 2998
欢迎使用Markdown编辑器 你好！ 这是你第一次使用 Markdown编辑器 所展示的欢迎页。如果你想学习如何使用Markdown编辑器, 可以仔细阅读这篇文章，了解一下Markdown的基本语法知识。 新的改变 我们对Markdown编辑器进行了一些功能拓展与语法支持，除了标准的Markdown编辑器功能，我们增加了如下几点新功能，帮助你用它写博客： 全新的界面设计 ，将会带来全新的写作体验； 在创作中心设置你喜爱的代码高亮样式，Markdown 将代码片显示选择的高亮样式 进行展示； 增加了 图片
redis登录常见报错
凉云半的博客
06-21 1798
redis
redis:Could not connect to Redis at 127.0.0.1:6379: Connection refused错误解析
热门推荐
渐行渐远
07-10 8万+
1.错误信息思考： 根据错误信息的字面意思，可以知道，redis-cli客户端程序，通过ip127.0.0.1,端口6379与redis服务器建立连接失败。说明当我们调用redis-cli时，默认是用本地回环地址去与服务器端建立连接。 2.解决问题思路： 服务器程序会在监听一个套接字(IP+端口号)，等待客户端的连接。一般运行服务器程序的时候，都会加载一个配置文件。 redis服务器也会读取一个配置文件。 如果不知道配置文件在哪里，可以使用： which redis.conf #或者 whe
redis关闭后在连接报错误：Could not connect to Redis at 127.0.0.1:6379: Connection refused
m0_61454947的博客
07-10 750
bug解决
解决Redis中Could not connect to Redis at 127.0.0.1:6380: Connection refused
最新发布
m0_68510526的博客
12-10 634
第二种解决方法：可能你的redis服务没有启动：通过systemctl start redis，这些都弄好还不行，通过vim编辑器看看你的配置文件slave.conf的端口号配置的是不是正确的。第一种解决方法：可能你没有启动你的结点：比如你的redis服务器的配置文件为slave.conf;那你先在你这个配置文件的目录下运行：redis-server ./slave.conf。
Redis主从复制和集群配置
08-21
### Redis主从复制和集群配置详解 #### 一、Redis主从复制原理及配置 **1.1 概述** Redis的主从复制机制是一种重要的数据同步方式，它支持一个或多个从数据库(slave)与主数据库(master)之间进行数据同步。其中，...
Redis主从复制以及主从复制技术原理.docx
10-14
Redis 主从复制技术原理 概述 Redis 是一个开源的使用 ANSI C 语言编写、支持网络、可基于内存亦可持久化的日志型、Key-Value 数据库，并提供多种语言的 API。Redis 主从复制是指将一台 Redis 服务器的数据，复制到...
通过SSRF操作Redis主从复制写Webshell_R3start1
08-03
1.使用 DICT 协议添加一条测试记录 2.设置保存路径 3.设置保存文件名 4.保存 1.连接远程主服务器 2.设置保存路径 3.设置保存文件名 4.保存
redis 安装 主从配置 选举
09-20
redis 安装 主从配置 redis 选举机制说明，
Redis 拒绝连接 Could not connect to Redis at 127.0.0.1:6379: Connection refused的几种情况
Hdu_lc14015312的博客
02-25 2万+
今天学Redis过程中遇到问题，拒绝连接： 通过查找，一般这种情况出现问题有两种： 第一种情况：一般本机拒绝访问就是出现了有其他IP地址在访问，删除其他访问进程（我失败的而原因是IDEA连接之后没关闭导致其他IP访问不了） 首先查看有没有其他IP访问Redis ps -ef | grep redis 果不其然，有其他IP访问 把这个进程杀死就好了 kill 1...
Could not connect to Redis at 127.0.0.1:6379: Connection refused
Forerunner and Successor 先駆者と後継者
11-27 3957
昨天，装好了redis，准备启程redis。不过，今天在linux开启redis的时候出了一个小问题，解决了，跟大家分享一下。 错误提示如下： 分析问题： 看一下是否是防火墙，或者是网络的问题，试一下ping服务，检查是否能够ping通，命令：ping 127.0.0.1，可以ping通，没有丢失数据包，证明网络没有问题。如下： 经过ping服务，发现并没有网络问题，那么可能是redis本身的服务问题。开启redis服务，命令：redis-server，如下： 开启redis服务，就不要关闭，把服务挂
redis-cli连接出现Could not connect to Redis at 127.0.0.1:6379: Connection refused
weixin_44726980的博客
05-01 2943
redis-cli连接时出现Could not connect to Redis at 127.0.0.1:6379: Connection refused 分析问题：redis-server(服务端)没启动 具体步骤 cd到redis的配置文件目录 [根据自己安装时的路径输入] cd /usr/local/etc/redis 修改redis的配置信息 [一定要加上sudo...
创建redis集群，第二次踩坑，Sorry, can't connect to node
波波的博客
06-07 1万+
这已经是第二次遇到这个问题，只记得第一次花了很长时间才解决，却忘了怎么解决的，悲催！网上找的答案都是各种复制，千篇一律。现在记下来，防止忘记！第一次是因为redis设置了密码，单机连接都OK，但是创建集群就报错Sorry, can't connect to node需要修改/usr/local/rvm/gems/ruby-2.4.1/gems/redis-4.0.1/lib/redis/clien...
redis连接时报错：Could not connect to Redis at 127.0.0.1:6379: Connection refused
ROY的博客
03-24 3万+
brew install redis 安装好redis用terminal连接redis时出现错误：Could not connect to Redis at 127.0.0.1:6379: Connection refused在/usr/local/etc/目录下找到redis.conf  将daemonize no 修改为 daemonize yes再输入 redis-server /usr/l...
-failover-abort-no-good-slave master
weixin_64161454的博客
03-13 1255
-failover-abort-no-good-slave masterr 在搭建redis哨兵监听集群状态时出现这个错误这个错误的意思表示选择附属从节点，转换主节点是出了错误，原因是没有好的从节点，根本原因就是没有找到从节点信息，出现这个错误的根本原因是在于我们的哨兵配置文件写错了
redis：哨兵选举新的master报错——-failover-abort-no-good-slave master mymaster
aflyingpig11的博客
09-27 506
3.sentinel.config 的sentinel monitor mymaster 和sentinel auth-pass mymaster 也没有错。但在我测试主从复制的时候，发现主从主机无法相连，我在网上找的解决方案的关闭了master主机所在的防火墙。1.我核对了sentinel.config和redis.config bind 绑定的端口。现在master下线了，需要选举新的master，需要关闭新master所在主机的防火墙。2.三台redis masterauth都设置了密码。
Redis集群部署3.0
baidu_31071595的博客
03-20 6977
Redis集群部署文档(centos6系统) （要让集群正常工作至少需要3个主节点，在这里我们要创建6个redis节点，其中三个为主节点，三个为从节点，对应的redis节点的ip和端口对应关系如下） 127.0.0.1:7000 127.0.0.1:7001 127.0.0.1:7002 127.0.0.1:7003 127.0.0.1:7004 127.0.
Redis主从复制详解与实战
"Redis主从复制技术的详细解析" Redis主从复制是Redis数据库系统中的一个重要特性，它允许数据在主节点（Master）和从节点（Slave）之间进行同步，以实现数据冗余、故障恢复、负载均衡以及高可用性的基础架构。在...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值