keepalived 切換的疑問

saup007

A：172.19.1.201
B：172.19.1.202
VIP：172.19.1.249

# /opt/keepalived/sbin/keepalived -v
Keepalived v1.2.19 (08/21,2015)

當(dāng)停掉A的MySQL，正常切換到B，當(dāng)把A MySQL啟來后，vip依然在B，這個(gè)符合邏輯，但把A MySQL啟來后，再去停掉B MySQL，VIP卻沒有飄移到A上，why？

若在B節(jié)點(diǎn)重啟keepalived，VIP會(huì)飄移到A的。


A:

vim keepalived.conf

1. #
   
2. ! Configuration File for keepalived
   
3. 
   
4. global_defs {
   
5.    notification_email {
   
6.      saup007@qq.com
   
7.    }
   
8.    notification_email_from root@dbaone
   
9.    smtp_server dbaone
   
10.    smtp_connect_timeout 30
    
11.    router_id MySQL-HA
    
12. }
    
13. 
    
14. vrrp_script chk_mysql_server {
    
15.    #script "/opt/keepalived/script/chk_mysql_server.sh"
    
16.    script "killall -0 mysqld"
    
17.    interval 30  # 檢測(cè)時(shí)間為30s
    
18.    weight 21
    
19. }
    
20. 
    
21. vrrp_instance VI_1 {
    
22.     state BACKUP
    
23.     interface eth1
    
24.     virtual_router_id 59
    
25.     priority 100
    
26.     advert_int 1
    
27.     nopreempt  # 非搶占模式,只在優(yōu)化級(jí)高的機(jī)器設(shè)置,優(yōu)先級(jí)低的不設(shè)置
    
28.     #mcast_src_ip 172.19.1.201
    
29.     authentication {
    
30.         auth_type PASS
    
31.         auth_pass 1111
    
32.     }
    
33.     notify_master "/opt/keepalived/script/master.sh"
    
34.     notify_backup "/opt/keepalived/script/backup.sh"
    
35.     notify_fault  "/opt/keepalived/script/fault.sh"
    
36.     notify_stop "/opt/keepalived/script/stop.sh"
    
37.     track_script {
    
38.         chk_mysql_server
    
39.     }
    
40.     virtual_ipaddress {
    
41.         172.19.1.249/24 dev eth1 scope global label eth1:0
    
42.     }
    
43. }

復(fù)制代碼

B:

vim keepalived.conf

1. #
   
2. ! Configuration File for keepalived
   
3. 
   
4. global_defs {
   
5.    notification_email {
   
6.      saup007@qq.com
   
7.    }
   
8.    notification_email_from root@dbatwo
   
9.    smtp_server dbatwo
   
10.    smtp_connect_timeout 30
    
11.    router_id MySQL-HA
    
12. }
    
13. 
    
14. vrrp_script chk_mysql_server {
    
15.    #script "/opt/keepalived/script/chk_mysql_server.sh"
    
16.    script "killall -0 mysqld"
    
17.    interval 30  # 檢測(cè)時(shí)間為30s
    
18.    weight 21
    
19. }
    
20. 
    
21. vrrp_instance VI_1 {
    
22.     state BACKUP
    
23.     interface eth1
    
24.     virtual_router_id 59
    
25.     priority 90
    
26.     advert_int 1
    
27.     #nopreempt  # 非搶占模式,只在優(yōu)化級(jí)高的機(jī)器設(shè)置,優(yōu)先級(jí)低的不設(shè)置
    
28.     #mcast_src_ip 172.19.1.202
    
29.     authentication {
    
30.         auth_type PASS
    
31.         auth_pass 1111
    
32.     }
    
33.     notify_master "/opt/keepalived/script/master.sh"
    
34.     notify_backup "/opt/keepalived/script/backup.sh"
    
35.     notify_fault  "/opt/keepalived/script/fault.sh"
    
36.     notify_stop "/opt/keepalived/script/stop.sh"
    
37.     track_script {
    
38.         chk_mysql_server
    
39.     }
    
40.     virtual_ipaddress {
    
41.         172.19.1.249/24 dev eth1 scope global label eth1:0
    
42.     }
    
43. }

復(fù)制代碼

saup007

暫時(shí)通過shell的方式實(shí)現(xiàn) B->A的飄移VIP ，不知能否通過keepalived本身來實(shí)現(xiàn)。

#
! Configuration File for keepalived

global_defs {
   notification_email {
     saup007@qq.com
   }
   notification_email_from root@dbatwo
   smtp_server dbatwo
   smtp_connect_timeout 30
   router_id MySQL-HA
}

vrrp_script chk_mysql_server {
   script "/opt/keepalived/script/chk_mysql_server.sh"
   #script "killall -0 mysqld"
   interval 30  # 檢測(cè)時(shí)間為30s
   weight -21
}

vrrp_instance VI_1 {
    state BACKUP
    interface eth1
    virtual_router_id 59
    priority 90
    advert_int 1
    #nopreempt  # 非搶占模式,只在優(yōu)化級(jí)高的機(jī)器設(shè)置,優(yōu)先級(jí)低的不設(shè)置
    #mcast_src_ip 172.19.1.202
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    notify_master "/opt/keepalived/script/master.sh"
    notify_backup "/opt/keepalived/script/backup.sh"
    notify_fault  "/opt/keepalived/script/fault.sh"
    notify_stop "/opt/keepalived/script/stop.sh"
    track_script {
        chk_mysql_server
    }
    virtual_ipaddress {
        172.19.1.249/24 dev eth1 scope global label eth1:0
    }
}

# cat /opt/keepalived/script/chk_mysql_server.sh
#!/bin/bash
killall -0 mysqld

if [[ $? -eq 0 ]]
then
   if [[ /tmp/keepalived ]]
   then
      rm -rf /tmp/keepalived
      exit 0;
   else
      exit 0;
   fi
else
   if [[ ! -f /tmp/keepalived ]]
   then
      /etc/init.d/keepalived restart
      echo "`date +%Y-%m-%d` keepalived" >> /tmp/keepalived
      exit 1;
   else
      exit 1;
   fi
fi

noshell

剛好最近也在玩這個(gè)，也遇到過這個(gè)問題。
1、timeout 5 我的參數(shù)是這個(gè)值
2、在”把A MySQL啟來后，再去停掉B MySQL，VIP卻沒有飄移到A上“。在B的keepalvie 是不是也沒停掉？
在控制腳本中加上，當(dāng)msql 停掉把keepalved 先停掉，并且把VIP去掉。然后再起keepalive. 這樣應(yīng)該就可以飄過去的。

saup007

回復(fù) 3# noshell


    A -> B 是不需要stop keepalive的，只需要優(yōu)先級(jí)就可以完成VIP飄移，但切換回來 B -> A，需要stop或restart keepalvied。