redis配置文件詳解及實現主從同步切換
原理：redis複製是怎麼進行工做node
-
若是設置了一個slave，無論是在第一次連接仍是從新連接master的時候，slave會發送一個同步命令 而後master開始後臺保存，收集全部對修改數據的命令。當後臺保存完成，master會將這個數據文件傳送到slave，而後保存在磁盤，加載到內存中；master接着發送收集到的全部的修改數據的命令，這比如一個流命令，是redis協議自己來實現的。redis
-
當master和slave因一些故障宕機時，slaves會自動的重鏈，若是master收到多個slave的同步請求，master會執行一個後臺保存，以確保全部的slaves都是正常的。 當master和slave可以維持連接，就會有一個完整的同步進行。數據庫
配置redis主從
-
配置主從同步是很簡單的，僅僅在slave的配置文件中增長相似下面這行的內容:vim
slaveof 192.168.1.1 6379bash
你能夠更換master的ip地址或地址，或者，你可使用slaveof命令，master就會啓動和slave的同步。服務器
-
設置slave到master的認證async
若是master須要經過密碼登錄，那就須要配置slave在進行全部同步操做也要使用到密碼。 在一個運行的實例上嘗試，使用 redis-cli :測試
config set masterauth <password>.net
你也能夠設置永久的。在配置文件中添加命令行
masterauth <password>
redis主從實戰
開啓主服務器的後臺運行,將配置文件中
daemonize no =》》 daemonize yes。
開啓從服務器的後臺運行，及設置slaveof的IP和端口：
vim redis.conf port 6379daemonize yes slaveof 192.168.1.21 6379
masterauth xxxxxxxx
主從切換
中止redis主服務器：
[root@localhost redis]# redis-cli -p 6379 shutdown [root@localhost redis]# redis-cli -p 6379 Could not connect to Redis at 127.0.0.1:6379: Connection refused not connected>
將redis從服務改成主：
#也能夠直接在數據庫命令行中輸入slaveof no one [root@localhost redis]# redis-cli -p 6379 slaveof NO ONEOK
假如原來的主redis恢復正常啦。要從新切換回去。
1). 將如今的主redis數據進行保存。
[root@localhost redis]# redis-cli
127.0.0.1:6379> save OK
2).將如今的主redis的dump.rdb文件拷貝到原來的主dump.rdb目錄下面
[root@localhost redis]# scp /data/redis/dump.rdb 192.168.1.21:/data/redis/dump.rdb
3).啓動原來的主redis
[root@localhost ~]# /usr/local/redis/bin/redis-server /usr/local/redis/redis.conf
4).將原來的從依然切換成從
[root@localhost redis]# redis-cli -p 6379 slaveof 192.168.1.21 6379 OK
這時你依然能夠讀取剛纔從庫寫入的數據，若是不能讀取則切換失敗。
在Master和Slave上安裝Keepalived 注意事項：主從的redis都要開啓本地備份
$ yum install keepalived
默認安裝完成keepalived有默認的配置文件，所以咱們重寫覆蓋它：
首先，在Master上建立以下配置文件：
$ vim /etc/keepalived/keepalived.conf
! Configuration File for keepalived
global_defs {
router_id redis100
}
vrrp_script chk_redis
{
script "/etc/keepalived/scripts/redis_check.sh 127.0.0.1 6379"
interval 2
timeout 2
fall 3
}
vrrp_instance redis {
state MASTER # master set to SLAVE also
interface eth0
virtual_router_id 50
priority 150
nopreempt # no seize,must add
advert_int 1
authentication { #all node must same
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
192.168.0.200/24
}
track_script {
chk_redis
}
notify_master "/etc/keepalived/scripts/redis_master.sh 127.0.0.1 192.168.0.101 6379"
notify_backup "/etc/keepalived/scripts/redis_backup.sh 127.0.0.1 192.168.0.101 6379"
notify_fault /etc/keepalived/scripts/redis_fault.sh
notify_stop /etc/keepalived/scripts/redis_stop.sh
}
而後，在Slave上建立以下配置文件：
! Configuration File for keepalived
global_defs {
router_id redis101
}
vrrp_script chk_redis
{
script "/etc/keepalived/scripts/redis_check.sh 127.0.0.1 6379"
interval 2
timeout 2
fall 3
}
vrrp_instance redis {
state BACKUP
interface eth0
virtual_router_id 50
priority 100
advert_int 1
authentication { #all node must same
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
192.168.0.200/24
}
track_script {
chk_redis
}
notify_master "/etc/keepalived/scripts/redis_master.sh 127.0.0.1 192.168.0.100 6379"
notify_backup "/etc/keepalived/scripts/redis_backup.sh 127.0.0.1 192.168.0.100 6379"
notify_fault /etc/keepalived/scripts/redis_fault.sh
notify_stop /etc/keepalived/scripts/redis_stop.sh
}
在Master和Slave上建立監控Redis的腳本
$ mkdir /etc/keepalived/scripts
$ vim /etc/keepalived/scripts/redis_check.sh
#!/bin/bash
ALIVE=`/usr/redis/redis-cli -h $1 -p $2 PING`
LOGFILE="/var/log/keepalived-redis-check.log"
echo "[CHECK]" >> $LOGFILE
date >> $LOGFILE
if [ $ALIVE == "PONG" ]; then :
echo "Success: redis-cli -h $1 -p $2 PING $ALIVE" >> $LOGFILE 2>&1
exit 0
else
echo "Failed:redis-cli -h $1 -p $2 PING $ALIVE " >> $LOGFILE 2>&1
exit 1
fi
編寫如下負責運做的關鍵腳本：
notify_master /etc/keepalived/scripts/redis_master.sh
notify_backup /etc/keepalived/scripts/redis_backup.sh
notify_fault /etc/keepalived/scripts/redis_fault.sh
notify_stop /etc/keepalived/scripts/redis_stop.sh
由於Keepalived在轉換狀態時會依照狀態來呼叫：
當進入Master狀態時會呼叫notify_master
當進入Backup狀態時會呼叫notify_backup
當發現異常狀況時進入Fault狀態呼叫notify_fault
當Keepalived程序終止時則呼叫notify_stop
首先，在Redis Master上建立notity_master與notify_backup腳本：
$ vim /etc/keepalived/scripts/redis_master.sh
#!/bin/bash
REDISCLI="/usr/redis/redis-cli -h $1 -p $3"
LOGFILE="/var/log/keepalived-redis-state.log"
echo "[master]" >> $LOGFILE
date >> $LOGFILE
echo "Being master...." >> $LOGFILE 2>&1
echo "Run MASTER cmd ..." >> $LOGFILE 2>&1
$REDISCLI SLAVEOF $2 $3 >> $LOGFILE
sleep 10 #delay 10 s wait data async cancel sync
echo "Run SLAVEOF NO ONE cmd ..." >> $LOGFILE
$REDISCLI SLAVEOF NO ONE >> $LOGFILE 2>&1
$ sudo vim /etc/keepalived/scripts/redis_backup.sh
#!/bin/bash
REDISCLI="/usr/redis/redis-cli"
LOGFILE="/var/log/keepalived-redis-state.log"
echo "[backup]" >> $LOGFILE
date >> $LOGFILE
echo "Run SLAVEOF cmd ..." >> $LOGFILE
$REDISCLI SLAVEOF $2 $3 >> $LOGFILE 2>&1
# echo "Being slave...." >> $LOGFILE 2>&1
sleep 15 #delay 15 s wait data sync exchange role
接着，在Redis Slave上建立notity_master與notify_backup腳本：
$ vim /etc/keepalived/scripts/redis_master.sh
#!/bin/bash
REDISCLI="/usr/redis/redis-cli -h $1 -p $3"
LOGFILE="/var/log/keepalived-redis-state.log"
echo "[master]" >> $LOGFILE
date >> $LOGFILE
echo "Being master...." >> $LOGFILE 2>&1
echo "Run SLAVEOF cmd ... " >> $LOGFILE
$REDISCLI SLAVEOF $2 $3 >> $LOGFILE 2>&1
#echo "SLAVEOF $2 cmd can't excute ... " >> $LOGFILE
sleep 10 ##delay 15 s wait data sync exchange role
echo "Run SLAVEOF NO ONE cmd ..." >> $LOGFILE
$REDISCLI SLAVEOF NO ONE >> $LOGFILE 2>&1
$ vim /etc/keepalived/scripts/redis_backup.sh
#!/bin/bash
REDISCLI="/usr/redis/redis-cli"
LOGFILE="/var/log/keepalived-redis-state.log"
echo "[BACKUP]" >> $LOGFILE
date >> $LOGFILE
echo "Being slave...." >> $LOGFILE 2>&1
echo "Run SLAVEOF cmd ..." >> $LOGFILE 2>&1
$REDISCLI SLAVEOF $2 $3 >> $LOGFILE
sleep 100 #delay 10 s wait data async cancel sync
exit(0)
而後在Master與Slave建立以下相同的腳本：
$ vim /etc/keepalived/scripts/redis_fault.sh
#!/bin/bash
LOGFILE=/var/log/keepalived-redis-state.log
echo "[fault]" >> $LOGFILE
date >> $LOGFILE
$ sudo vim /etc/keepalived/scripts/redis_stop.sh
#!/bin/bash
LOGFILE=/var/log/keepalived-redis-state.log
echo "[stop]" >> $LOGFILE
date >> $LOGFILE
給腳本都加上可執行權限：
（這點很重要,最開始因爲這不沒作，運行後一直報錯 "VRRP_Instance(Redis) Now in FAULT state"）
$ sudo chmod +x /etc/keepalived/scripts/*.sh
腳本建立完成之後，咱們開始按照以下流程進行測試：1.啓動Master上的Redis$ /etc/init.d/redis start2.啓動Slave上的Redis$ /etc/init.d/redis start3.啓動Master上的Keepalived$ /etc/init.d/keepalived start4.啓動Slave上的Keepalived$ /etc/init.d/keepalived start5.嘗試經過VIP鏈接Redis:$ redis-cli -h 10.6.1.200 INFO鏈接成功，Slave也鏈接上來了。role:masterslave0:10.6.1.144,6379,online6.嘗試插入一些數據：$ redis-cli -h 10.6.1.200 SET Hello RedisOK從VIP讀取數據$ redis-cli -h 10.6.1.200 GET Hello"Redis"從Master讀取數據$ redis-cli -h 10.6.1.143 GET Hello"Redis"從Slave讀取數據$ redis-cli -h 10.6.1.144 GET Hello"Redis"下面，模擬故障產生：將Master上的Redis停了$ service redis_6379 stop查看Master上的Keepalived日誌$ tailf /var/log/keepalived-redis-state.log[fault]Thu Sep 27 08:29:01 CST 2012同時Slave上的日誌顯示：$ tailf /var/log/keepalived-redis-state.log[master]Fri Sep 28 14:14:09 CST 2012Being master....Run SLAVEOF cmd ...OKRun SLAVEOF NO ONE cmd ...OK而後咱們能夠發現，Slave已經接管服務，而且擔任Master的角色了。$ redis-cli -h 192.168.0.200 INFOrole:master而後咱們恢復Master的Redis進程$ service redis_6379 start查看Master上的Keepalived日誌$ tailf /var/log/keepalived-redis-state.log[master]Thu Sep 27 08:31:33 CST 2012Being master....Run SLAVEOF cmd ...OKRun SLAVEOF NO ONE cmd ...OK同時Slave上的日誌顯示：$ tailf /var/log/keepalived-redis-state.log[backup]Fri Sep 28 14:16:37 CST 2012Being slave....Run SLAVEOF cmd ...OK能夠發現目前的Master已經再次恢復了Master的角色，故障切換以及自動恢復都成功了。
- 1. redis主從配置及主從切換
- 2. Redis主從同步之主從切換
- 3. redis配置主從同步
- 4. redis主從同步配置
- 5. Redis主從同步+自動切換
- 6. redis用zookeeper實現自動主從同步，切換
- 7. mysql主從同步配置詳解
- 8. centos7.7+mysql5.7主從同步配置詳解
- 9. redis sentinel 主從切換(failover)解決方案，詳細配置
- 10. redis sentinel 主從切換(failover)解決方案、詳細配置
- 更多相關文章...
- • MyBatis配置文件詳解 - MyBatis教程
- • *.hbm.xml映射文件詳解 - Hibernate教程
- • Flink 數據傳輸及反壓詳解
- • IDEA下SpringBoot工程配置文件沒有提示
-
每一个你不满意的现在，都有一个你没有努力的曾经。