appendfsync everysec
2|0主從同步
redis主從同步實(shí)現(xiàn)
1.準(zhǔn)備三個(gè)redis數(shù)據(jù)庫(kù),redis支持多實(shí)例
三個(gè)配置文件,僅僅是端口的不同
在三個(gè)配置文件中,添加主從同步的參數(shù)
redis-6379.conf
port 6379 daemonize yes pidfile /data/6379/redis.pid loglevel notice logfile "/data/6379/redis.log" dir /data/6379 protected-mode yes dbfilename dbmp.rdb save 900 1 save 300 10 save 60 10000
redis-6380.conf
port 6380 daemonize yes pidfile /data/6380/redis.pid loglevel notice logfile "/data/6380/redis.log" dir /data/6380 protected-mode yes dbfilename dbmp.rdb save 900 1 save 300 10 save 60 10000 slaveof 127.0.0.1 6379
redis-6381.conf
port 6381 daemonize yes pidfile /data/6381/redis.pid loglevel notice logfile "/data/6381/redis.log" dir /data/6381 protected-mode yes dbfilename dbmp.rdb save 900 1 save 300 10 save 60 10000 slaveof 127.0.0.1 6379
2.啟動(dòng)三個(gè)數(shù)據(jù)庫(kù)實(shí)例,查看主從同步身份
redis-cli -p 6379 info replication redis-cli -p 6380 info replication redis-cli -p 6381 info replication
3:確保查看信息如下 并且檢查是否同步
4.如果我主庫(kù)掛了怎么辦??
解決方案:
1.手動(dòng)切換主從身份,選舉一個(gè)新的主庫(kù)
1.干掉6379主庫(kù)
2.在6380上關(guān)閉自己的slave身份
slaveof no one
3.在6381上給與新的主人身份
salveof 127.0.0.1 6380
4.修改完畢,還得修改配置文件,永久生效
2,用哨兵自動(dòng)選舉新主人
2|1redis哨兵:
哨兵功能:
哨兵進(jìn)行檢測(cè),主從架構(gòu)是否正常,如果主庫(kù)掛掉,哨兵會(huì)自動(dòng)的修改redis.conf,進(jìn)行添加/刪除 slaveof 指令
redis哨兵安裝配置:
1.準(zhǔn)備三個(gè)redis實(shí)例,一主兩從
詳見上面redis主從配置
2,準(zhǔn)備好了三個(gè)數(shù)據(jù)庫(kù)實(shí)例,啟動(dòng)三個(gè)數(shù)據(jù)庫(kù)實(shí)例
redis-server redis-6379.conf redis-server redis-6380.conf redis-server redis-6381.conf
3,準(zhǔn)備三個(gè)哨兵,開始監(jiān)控主從架構(gòu)
準(zhǔn)備三個(gè)配置文件,哨兵文件
redis-26379.conf
port 26379 dir /var/redis/data/ logfile "26379.log" sentinel monitor sbmaster 127.0.0.1 6379 2 sentinel down-after-milliseconds qsmaster 30000 sentinel parallel-syncs sbmaster 1 sentinel failover-timeout sbmaster 180000 daemonize yes
redis-26380.conf
port 26380 dir /var/redis/data/ logfile "26380.log" sentinel monitor sbmaster 127.0.0.1 6379 2 sentinel down-after-milliseconds qsmaster 30000 sentinel parallel-syncs sbmaster 1 sentinel failover-timeout sbmaster 180000 daemonize yes
redis-26381.conf
port 26381 dir /var/redis/data/ logfile "26381.log" sentinel monitor sbmaster 127.0.0.1 6379 2 sentinel down-after-milliseconds sbmaster 30000 sentinel parallel-syncs sbmaster 1 sentinel failover-timeout sbmaster 180000 daemonize yes
4,啟動(dòng)三個(gè)哨兵實(shí)例
redis-sentinel redis-26380.conf redis-sentinel redis-26379.conf redis-sentinel redis-26381.conf
檢查哨兵狀態(tài)是否正常
只有發(fā)現(xiàn)如下信息,與下面一致,即為正常
redis-cli -p 26379 info sentinel
# Sentinel sentinel_masters:1 sentinel_tilt:0 sentinel_running_scripts:0 sentinel_scripts_queue_length:0 sentinel_simulate_failure_flags:0 master0:name=sbmaster,status=ok,address=127.0.0.1:6380,slaves=2,sentinels=3
5,進(jìn)行哨兵自動(dòng)主從切換
1.干掉6379的redis數(shù)據(jù)庫(kù)
2.查看6380和6381的身份信息,是否自動(dòng)的進(jìn)行主從切換(需等待30秒才會(huì)切換)
3.手動(dòng)啟動(dòng)6379掛掉的數(shù)據(jù)庫(kù),查看是否會(huì)被哨兵,添加進(jìn)信息的主從集群
注意?。∪绻l(fā)現(xiàn)不成功,需刪掉所有的哨兵配置文件,從新來過