概念
主从复制,是指将一台Redis服务器的数据,复制到其他的Redis服务器。前者称为主节点(masterleader) ,后者称为从节点
(slavefolldwer) ;==数据的复制是单向的,只能由主节点到从节点==。Master以写为主, Slave以读为主
==默认情况下,每台Redis服务器都是主节点==;且一个主节点可以有多个从节点(或没有从节点),但一个从节点只能有一个主节点。
作用
主从复制的作用主要包括:
- 数据冗余:主从复制实现了数据的热备份,是持久化之外的一种数据冗余方式。
- 故障恢复:当主节点出现问题时,可以由从节点提供服务,实现快速的故障恢复;实际上是一种服务的冗余。
- 负载均衡:在主从复制的基础上,配合读写分离,可以由主节点提供写服务,由从节点提供读服务(即写Redis数据时应用连接
主节点,读Redis数据时应用连接从节点) ,分担服务器负载;尤其是在写少读多的场景下,通过多个从节点分担读负载,可以大
大提高Redis服务器的并发量。 - 高可用基石:除了上述作用以外,主从复制还是哨兵和集群能够实施的基础,因此说主从复制是Redis高可用的基础。
一般来说,要将Redis运用于工程项目中,只使用一台Redis是万万不能的(宕机) ,原因如下:
- 从结构上,单个Redis服务器会发生单点故障,并且一台服务器需要处理所有的请求负载,压力较大;
- 从容量上,单个Redis服务器内存容量有限,就算一台Redis服务器内存容量为256G,也不能将所有内存用作Redis存储内存
一般来说,单台Redis最大使用内存不应该超过20G
电商网站上的商品,一般都是一次上传,无数次浏览的,说专业点也就是”多读少写”。
环境搭建
主从信息查询
127.0.0.1:6379> info replication #查看主从信息
# Replication
role:master # 角色,是主机还是从机
connected_slaves:0 # 从机个数
master_failover_state:no-failover
master_replid:95e7380696b57cef74de81d4673e127a7619fda0
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配置文件修改项(避免重复覆盖)
- 端口号
- PID文件
- Log文件
- rdb文件
第一种方式
graph LR
主机A-->从机B
主机A-->从机C配置信息
配置从机
命令配置
# 配置主机IP和端口 127.0.0.1:6380> SLAVEOF 127.0.0.1 6379 OK配置文件配置
replicaof 127.0.0.1 6379从机信息
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:1
master_sync_in_progress:0
slave_repl_offset:14
slave_priority:100
slave_read_only:1
replica_announced:1
connected_slaves:0
master_failover_state:no-failover
master_replid:cf02d21e7fd2d53056311c0c1550e0d08c02c789
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:14
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:14主机信息
127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:2
slave0:ip=127.0.0.1,port=6380,state=online,offset=224,lag=1
slave1:ip=127.0.0.1,port=6381,state=online,offset=224,lag=1
master_failover_state:no-failover
master_replid:cf02d21e7fd2d53056311c0c1550e0d08c02c789
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:224
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:224功能测试
从机自动同步
#主机设置值
127.0.0.1:6379> set k3 v3
OK
#从机自动同步
127.0.0.1:6380> keys *
1) "k3"
2) "k1"
3) "k2"从机只读
127.0.0.1:6381> set k4 v4
(error) READONLY You can't write against a read only replica.主机断开
#主机断开(宕机)
127.0.0.1:6379> shutdown
not connected>
#从机默认依旧作为从机连接主机
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:17062
master_link_down_since_seconds:7
slave_priority:100
slave_read_only:1
replica_announced:1
connected_slaves:0
master_failover_state:no-failover
master_replid:cf02d21e7fd2d53056311c0c1550e0d08c02c789
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:17062
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:183
repl_backlog_histlen:16880主机断开后,从机依旧作为从机连接主机,集群就只有读功能,没有写操作。如果主机回来,从机依旧可以直接获取到主机信息。配置哨兵模式后,可以自动选举一个作为主机。
如果使用命令行配置主从,是不持久的,如果重启了,就会变回主机。配置文件中配置主从是持久生效的。
从机成功连接到主机后,会发送一个sync同步命令。主机接到命令,启动后台的存盘进程,同时收集所有接收到的用于修改数据集命令,在后台进程执行完毕之后,主机将传送整个数据文件到从机,并完成一次完全同步(==这个叫全量复制,后面主机新增值,依次将修改命令传给从机执行,叫做增量复制==)。
第二种方式
graph LR
主机A-->从机B
从机B-->从机C配置信息
从机A
slaveof 127.0.0.1 6379从机B
slaveof 127.0.0.1 6380功能测试
主机断开,从机手动变为主机
slaveof no one从机B当选主机,从机C连接B
127.0.0.1:6380> info replication
# Replication
role:master
connected_slaves:1
slave0:ip=127.0.0.1,port=6381,state=online,offset=1288,lag=0
master_failover_state:no-failover
master_replid:a7131f2ad29e3d74b13249f34c96851590a3c988
master_replid2:7fb1815699259ae0976825b8385930bddd79837f
master_repl_offset:1288
second_repl_offset:99
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:43
repl_backlog_histlen:1246主机A重启后,B依然当主机
127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:0
master_failover_state:no-failover
master_replid:ccc698a2310cd9e474745d6943768e2c70d942c0
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
第三种:哨兵模式(自动选举)
graph LR
哨兵-->主机A
主机A-->从机B
哨兵-->从机B
哨兵-->从机C
主机A-->从机C配置
vim sentinel.conf
sentinel monitor myredis 127.0.0.1 6379 1启动
doubly@xiaoyizideMacBook-Pro bin % redis-sentinel doublyConfig/sentinel.conf
66451:X 28 Jun 2021 13:39:32.117 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
66451:X 28 Jun 2021 13:39:32.117 # Redis version=6.2.4, bits=64, commit=00000000, modified=0, pid=66451, just started
66451:X 28 Jun 2021 13:39:32.117 # Configuration loaded
66451:X 28 Jun 2021 13:39:32.119 * Increased maximum number of open files to 10032 (it was originally set to 256).
66451:X 28 Jun 2021 13:39:32.119 * monotonic clock: POSIX clock_gettime
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.2.4 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in sentinel mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 26379
| `-._ `._ / _.-' | PID: 66451
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | https://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
66451:X 28 Jun 2021 13:39:32.124 # Sentinel ID is 8c6e1549c754881a4f65cc855dfb9569409762a1
66451:X 28 Jun 2021 13:39:32.124 # +monitor master myredis 127.0.0.1 6379 quorum 1
66451:X 28 Jun 2021 13:39:32.127 * +slave slave 127.0.0.1:6380 127.0.0.1 6380 @ myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:39:32.129 * +slave slave 127.0.0.1:6381 127.0.0.1 6381 @ myredis 127.0.0.1 6379主机shutdown后的哨兵日志
66451:X 28 Jun 2021 13:42:26.257 # +sdown master myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.257 # +odown master myredis 127.0.0.1 6379 #quorum 1/1
66451:X 28 Jun 2021 13:42:26.257 # +new-epoch 1
66451:X 28 Jun 2021 13:42:26.257 # +try-failover master myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.261 # +vote-for-leader 8c6e1549c754881a4f65cc855dfb9569409762a1 1
66451:X 28 Jun 2021 13:42:26.261 # +elected-leader master myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.261 # +failover-state-select-slave master myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.330 # +selected-slave slave 127.0.0.1:6381 127.0.0.1 6381 @ myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.330 * +failover-state-send-slaveof-noone slave 127.0.0.1:6381 127.0.0.1 6381 @ myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.414 * +failover-state-wait-promotion slave 127.0.0.1:6381 127.0.0.1 6381 @ myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.820 # +promoted-slave slave 127.0.0.1:6381 127.0.0.1 6381 @ myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.820 # +failover-state-reconf-slaves master myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:26.876 * +slave-reconf-sent slave 127.0.0.1:6380 127.0.0.1 6380 @ myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:27.881 * +slave-reconf-inprog slave 127.0.0.1:6380 127.0.0.1 6380 @ myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:27.881 * +slave-reconf-done slave 127.0.0.1:6380 127.0.0.1 6380 @ myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:27.961 # +failover-end master myredis 127.0.0.1 6379
66451:X 28 Jun 2021 13:42:27.961 # +switch-master myredis 127.0.0.1 6379 127.0.0.1 6381
66451:X 28 Jun 2021 13:42:27.962 * +slave slave 127.0.0.1:6380 127.0.0.1 6380 @ myredis 127.0.0.1 6381
66451:X 28 Jun 2021 13:42:27.962 * +slave slave 127.0.0.1:6379 127.0.0.1 6379 @ myredis 127.0.0.1 6381
66451:X 28 Jun 2021 13:42:58.037 # +sdown slave 127.0.0.1:6379 127.0.0.1 6379 @ myredis 127.0.0.1 63816380自动指向6381
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:2
master_sync_in_progress:0
slave_repl_offset:34018
slave_priority:100
slave_read_only:1
replica_announced:1
connected_slaves:0
master_failover_state:no-failover
master_replid:9eccaf8f6170f964eab0efa6e894526fc243fda3
master_replid2:d25e84c3694901fea82095385a55d5f487014a28
master_repl_offset:34018
second_repl_offset:9600
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:340186381被选举为主机
127.0.0.1:6381> info replication
# Replication
role:master
connected_slaves:1
slave0:ip=127.0.0.1,port=6380,state=online,offset=38750,lag=1
master_failover_state:no-failover
master_replid:9eccaf8f6170f964eab0efa6e894526fc243fda3
master_replid2:d25e84c3694901fea82095385a55d5f487014a28
master_repl_offset:38750
second_repl_offset:9600
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:38750==重新连回来的主机被归并到6381做从机==
127.0.0.1:6381> info replication
# Replication
role:master
connected_slaves:2
slave0:ip=127.0.0.1,port=6380,state=online,offset=47931,lag=1
slave1:ip=127.0.0.1,port=6379,state=online,offset=47931,lag=0
master_failover_state:no-failover
master_replid:9eccaf8f6170f964eab0efa6e894526fc243fda3
master_replid2:d25e84c3694901fea82095385a55d5f487014a28
master_repl_offset:48063
second_repl_offset:9600
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:48063