MySQL的高可用方案有很多，比如Cluster，MMM，MHA，DRBD等，这些都比较复杂，我前面的文章也有介绍。最近Oracle官方也推出了Fabric。有时我们不需要这么复杂的环境，这些方案各有优劣。有时简单的且我们能够hold住的方案才是适合我们的。比如MySQL Replication，然后加上各种高可用软件，比如Keepalived等，就能实现我们需要的高可用环境。

MySQL架构为master/slave，当master故障时，vip漂移到slave上。提供服务。当然也可以设置为双master，但是不是每个方案都是完美的。这里设置为双master有个问题需要注意，比如，当用户发表文章时，由于此时主机的压力很大时，假设落后2000秒，那么这台主机宕机了，另一台主机接管（vip漂移到从机上）时，因为同步延时大，用户刚才发表的文章还没复制过来，于是用户又发表了一遍文章，当原来的master修复好后，由于I/O和SQL线程还处于开启状态，因此还会继续同步刚才没有同步复制完的数据，这时有可能把用户新发表的文章更改掉。这里所以采用master/slave架构。在这种架构中，故障切换以后，采取手动操作的方式与新的master进行复制。

简单环境如下：

master     192.168.0.100

slave      192.168.0.101

VIP        192.168.0.88

主从复制环境的搭建我这里就不演示了。有需要的同学自己看看官方手册。下面直接介绍keepalived的安装及配置使用。

1.keepalived软件安装（主从操作一样）

[root@mysql-server- ~]# wget -q http://www.keepalived.org/software/keepalived-1.2.13.tar.gz

[root@mysql-server- ~]# tar xf keepalived-1.2..tar.gz

[root@mysql-server- ~]# cd keepalived-1.2.

[root@mysql-server- keepalived-1.2.]# ./configure && make && make install
[root@mysql-server- keepalived]# cp /usr/local/etc/rc.d/init.d/keepalived /etc/rc.d/init.d/

[root@mysql-server- keepalived]# cp /usr/local/etc/sysconfig/keepalived /etc/sysconfig/

[root@mysql-server- keepalived]# mkdir /etc/keepalived

[root@mysql-server- keepalived]# cp /usr/local/etc/keepalived/keepalived.conf /etc/keepalived/

[root@mysql-server- keepalived]# cp /usr/local/sbin/keepalived /usr/sbin/

[root@mysql-server- keepalived]# chkconfig --add keepalived

[root@mysql-server- keepalived]# chkconfig --level  keepalived on

2.主从的配置文件修改（主的keepalived配置文件修改后如下，其实不相同的就优先级而已）
master的keepalived配置文件如下

[root@mysql-server- keepalived]# cat keepalived.conf

global_defs {

   router_id MySQL-HA

} 

vrrp_script check_run {

script "/data/sh/mysql_check.sh"

interval

}

vrrp_sync_group VG1 {

group {

VI_1

}

}

vrrp_instance VI_1 {

    state BACKUP

    interface eth1

    virtual_router_id

    priority

    advert_int

    nopreempt

    authentication {

        auth_type PASS

        auth_pass

    }

    track_script {

    check_run

    }

    notify_master /data/sh/master.sh

    notify_backup /data/sh/backup.sh

    notify_stop /data/sh/stop.sh

    virtual_ipaddress {

        192.168.0.88

    }

}

[root@mysql-server- keepalived]#

slave的keepalived配置文件修改以后如下：

[root@mysql-server- keepalived]# cat keepalived.conf

global_defs {

   router_id MySQL-HA

} 

vrrp_script check_run {

script "/data/sh/mysql_check.sh"

interval

}

vrrp_sync_group VG1 {

group {

VI_1

}

}

vrrp_instance VI_1 {

    state BACKUP

    interface eth1

    virtual_router_id

    priority

    advert_int

    authentication {

        auth_type PASS

        auth_pass

    }

    track_script {

    check_run

    }

    notify_master /data/sh/master.sh

    notify_backup /data/sh/backup.sh

    notify_stop /data/sh/stop.sh

    virtual_ipaddress {

        192.168.0.88

    }

}

[root@mysql-server- keepalived]#

其中有几个关键参数的地方：
notify_master：状态改变为master以后执行的脚本。

notify_backup: 状态改变为backup以后执行的脚本。

notify_fault: 状态改变为fault后执行的脚本。

notify_stop: VRRP停止以后执行的脚本。

state backup：我们都设置为了backup，就是为了发生故障以后不会自动切换。

nopreempt： 不进行抢占操作

其中用到了这4个脚本：backup.sh  master.sh  mysql_check.sh  stop.sh

mysql_check.sh是为了检查mysqld进程是否存活的脚本，当发现连接不上mysql，自动把keepalived进程干掉，让VIP进行漂移。

下面的脚本主从服务器上面都有，只是从服务器上面的master.sh有些不一样。添加了当slave提升为主库时，发送邮件通知。

[root@mysql-server- sh]# cat mysql_check.sh

#!/bin/bash

. /root/.bash_profile

count=

while true

do

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14520.sock -e "show status;" > /dev/null >&

i=$?

ps aux | grep mysqld | grep -v grep > /dev/null >&

j=$?

if [ $i =  ] && [ $j =  ]

then

   exit

else

   if [ $i =  ] && [ $j =  ]

   then

       exit

   else

        if [ $count -gt  ]

        then

              break

        fi

   let count++

   continue

   fi

fi

done

/etc/init.d/keepalived stop

[root@mysql-server- sh]#

master.sh的作用是状态改为master以后执行的脚本。首先判断复制是否有延迟，如果有延迟，等1分钟后，不论是否有延迟。都跳过，并停止复制。并且授权账号，记录binlog和pos点。

[root@mysql-server- sh]# cat master.sh

#!/bin/bash

. /root/.bash_profile

Master_Log_File=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show slave status\G" | grep -w Master_Log_File | awk -F": " '{print $2}')

Relay_Master_Log_File=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show slave status\G" | grep -w Relay_Master_Log_File | awk -F": " '{print $2}')

Read_Master_Log_Pos=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show slave status\G" | grep -w Read_Master_Log_Pos | awk -F": " '{print $2}')

Exec_Master_Log_Pos=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show slave status\G" | grep -w Exec_Master_Log_Pos | awk -F": " '{print $2}')

i=

while true

do

if [ $Master_Log_File = $Relay_Master_Log_File ] && [ $Read_Master_Log_Pos -eq $Exec_Master_Log_Pos ]

then

   echo "ok"

   break

else

   sleep 

   if [ $i -gt  ]

   then

      break

   fi

   continue

   let i++

fi

done

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "stop slave;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global innodb_support_xa=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global sync_binlog=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global innodb_flush_log_at_trx_commit=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "flush logs;GRANT ALL PRIVILEGES ON *.* TO 'admin'@'%' IDENTIFIED BY '123456';flush privileges;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show master status;" > /tmp/master_status_$(date "+%y%m%d-%H%M").txt

[root@mysql-server- sh]#

slave上的master.sh

[root@mysql-server- sh]# cat master.sh

#!/bin/bash

. /root/.bash_profile

Master_Log_File=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show slave status\G" | grep -w Master_Log_File | awk -F": " '{print $2}')

Relay_Master_Log_File=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show slave status\G" | grep -w Relay_Master_Log_File | awk -F": " '{print $2}')

Read_Master_Log_Pos=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show slave status\G" | grep -w Read_Master_Log_Pos | awk -F": " '{print $2}')

Exec_Master_Log_Pos=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show slave status\G" | grep -w Exec_Master_Log_Pos | awk -F": " '{print $2}')

i=

while true

do

if [ $Master_Log_File = $Relay_Master_Log_File ] && [ $Read_Master_Log_Pos -eq $Exec_Master_Log_Pos ]

then

   echo "ok"

   break

else

   sleep 

   if [ $i -gt  ]

   then

      break

   fi

   continue

   let i++

fi

done

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "stop slave;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global innodb_support_xa=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global sync_binlog=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global innodb_flush_log_at_trx_commit=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "flush logs;GRANT ALL PRIVILEGES ON *.* TO 'admin'@'%' IDENTIFIED BY '123456';flush privileges;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show master status;" > /tmp/master_status_$(date "+%y%m%d-%H%M").txt

#当slave提升为主以后，发送邮件

echo "#####################################" > /tmp/status

echo "salve已经提升为主库，请进行检查！" >> /tmp/status

ifconfig | sed -n '/inet /{s/.*addr://;s/ .*//;p}' | grep -v 127.0.0.1 >> /tmp/status

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -Nse "show variables like 'port'" >> /tmp/status

echo "#####################################" >> /tmp/status

master=`cat /tmp/status`

echo "$master" | mutt -s "slave to primary!!!" @.com

脚本中检查复制是否延时的思想如下：
1、首先看 Relay_Master_Log_File 和 Master_Log_File 是否有差异
2、如果Relay_Master_Log_File 和 Master_Log_File 有差异的话，那说明延迟很大了
3、如果Relay_Master_Log_File 和 Master_Log_File 没有差异，再来看Exec_Master_Log_Pos 和 Read_Master_Log_Pos 的差异

而不是通过Seconds_Behind_Master去判断，该值表示slave上SQL线程和IO线程之间的延迟，实际上还要考虑到 Master_Log_File 和 Relay_Master_Log_File 是否有差距，更严谨的则是要同时在master上执行show master status进行对比。这也是MHA在切换过程中可以做到的。MMM的切换也只是在从库上执行了show slave status。所以数据一致性要求还是MHA给力。扯远了。^_^

backup.sh脚本的作用是状态改变为backup以后执行的脚本。

[root@mysql-server- sh]# cat backup.sh

#!/bin/bash

. /root/.bash_profile

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "GRANT ALL PRIVILEGES ON *.* TO 'admin'@'%' IDENTIFIED BY '123456';flush privileges;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global event_scheduler=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global innodb_support_xa=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global sync_binlog=0;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global innodb_flush_log_at_trx_commit=0;"

stop.sh 表示keepalived停止以后需要执行的脚本。更改密码，设置参数，检查是否还有写入操作，最后无论是否执行完毕，都退出。

[root@mysql-server- sh]# cat stop.sh

#!/bin/bash

. /root/.bash_profile

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "GRANT ALL PRIVILEGES ON *.* TO 'admin'@'%' IDENTIFIED BY '1q2w3e4r';flush privileges;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global innodb_support_xa=1;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global sync_binlog=1;"

mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "set global innodb_flush_log_at_trx_commit=1;"

M_File1=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show master status\G" | awk -F': ' '/File/{print $2}')

M_Position1=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show master status\G" | awk -F': ' '/Position/{print $2}')

sleep

M_File2=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show master status\G" | awk -F': ' '/File/{print $2}')

M_Position2=$(mysql -uroot -pmsandbox -S /tmp/mysql_sandbox14521.sock -e "show master status\G" | awk -F': ' '/Position/{print $2}')

i=

while true

do

if [ $M_File1 = $M_File1 ] && [ $M_Position1 -eq $M_Position2 ]

then

   echo "ok"

   break

else

   sleep 

   if [ $i -gt  ]

   then

      break

   fi

   continue

   let i++

fi

done

[root@mysql-server- sh]#

到这里基本就介绍完了。最后我们先看主从复制是否正常，如果正常，然后分别启动keepalived，然后进行故障切换测试。

slave状态：

node2 [localhost] {msandbox} ((none)) > pager cat | egrep 'Master_Log_File|Relay_Master_Log_File|Read_Master_Log_Pos|Exec_Master_Log_Pos|Running'

PAGER set to 'cat | egrep 'Master_Log_File|Relay_Master_Log_File|Read_Master_Log_Pos|Exec_Master_Log_Pos|Running''

node2 [localhost] {msandbox} ((none)) > show slave status\G

              Master_Log_File: mysql-bin.000001

          Read_Master_Log_Pos: 409

        Relay_Master_Log_File: mysql-bin.000001

             Slave_IO_Running: Yes

            Slave_SQL_Running: Yes

          Exec_Master_Log_Pos: 409

      Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it

1 row in set (0.00 sec)

node2 [localhost] {msandbox} ((none)) >

master 状态：

node1 [localhost] {msandbox} ((none)) > show master status;

+------------------+----------+--------------+------------------+-------------------+

| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

+------------------+----------+--------------+------------------+-------------------+

| mysql-bin.000001 |      409 |              |                  |                   |

+------------------+----------+--------------+------------------+-------------------+

1 row in set (0.00 sec)

node1 [localhost] {msandbox} ((none)) >

根据我前面给的判断条件，可以看出我的复制没有任何延时。
下面分别在master上和slave上启动keepalived进程。以及查看日志（上面的查看只是给大家说明如何判断复制是否延迟）

master

[root@mysql-server- sh]# /etc/init.d/keepalived start

Starting keepalived:                                       [  OK  ]

[root@mysql-server- sh]# tail -f /var/log/messages

Jul  :: mysql-server- Keepalived_vrrp[]: Netlink reflector reports IP 192.168.87.134 added

Jul  :: mysql-server- Keepalived_vrrp[]: Netlink reflector reports IP 192.168.0.100 added

Jul  :: mysql-server- Keepalived_vrrp[]: Registering Kernel netlink reflector

Jul  :: mysql-server- Keepalived_vrrp[]: Registering Kernel netlink command channel

Jul  :: mysql-server- Keepalived_vrrp[]: Registering gratuitous ARP shared channel

Jul  :: mysql-server- Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.0.100 added

Jul  :: mysql-server- Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.87.134 added

Jul  :: mysql-server- Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.0.100 added

Jul  :: mysql-server- Keepalived_healthcheckers[]: Registering Kernel netlink reflector

Jul  :: mysql-server- Keepalived_healthcheckers[]: Registering Kernel netlink command channel

Jul  :: mysql-server- Keepalived_healthcheckers[]: Opening file '/etc/keepalived/keepalived.conf'.

Jul  :: mysql-server- Keepalived_healthcheckers[]: Configuration is using :  Bytes

Jul  :: mysql-server- Keepalived_vrrp[]: Opening file '/etc/keepalived/keepalived.conf'.

Jul  :: mysql-server- Keepalived_vrrp[]: Configuration is using :  Bytes

Jul  :: mysql-server- Keepalived_vrrp[]: Using LinkWatch kernel netlink reflector...

Jul  :: mysql-server- Keepalived_healthcheckers[]: Using LinkWatch kernel netlink reflector...

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Entering BACKUP STATE

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP sockpool: [ifindex(), proto(), unicast(), fd(,)]

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Script(check_run) succeeded

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Transition to MASTER STATE

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Group(VG1) Syncing instances to MASTER state

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Entering MASTER STATE

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) setting protocol VIPs.

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.0.88

Jul  :: mysql-server- Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.0.88 added

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.0.88

slave

[root@mysql-server- tmp]# /etc/init.d/keepalived start

Starting keepalived:                                       [  OK  ]

[root@mysql-server- tmp]# tail -f /var/log/messages

Jul  :: mysql-server- Keepalived_vrrp[]: Netlink reflector reports IP fe80::20c:29ff:fefe:dc91 added

Jul  :: mysql-server- Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.0.101 added

Jul  :: mysql-server- Keepalived_healthcheckers[]: Netlink reflector reports IP fe80::20c:29ff:fefe:dc91 added

Jul  :: mysql-server- Keepalived_vrrp[]: Netlink reflector reports IP fe80::20c:29ff:fefe:dc9b added

Jul  :: mysql-server- Keepalived_vrrp[]: Registering Kernel netlink reflector

Jul  :: mysql-server- Keepalived_healthcheckers[]: Netlink reflector reports IP fe80::20c:29ff:fefe:dc9b added

Jul  :: mysql-server- Keepalived_healthcheckers[]: Registering Kernel netlink reflector

Jul  :: mysql-server- Keepalived_vrrp[]: Registering Kernel netlink command channel

Jul  :: mysql-server- Keepalived_healthcheckers[]: Registering Kernel netlink command channel

Jul  :: mysql-server- Keepalived_vrrp[]: Registering gratuitous ARP shared channel

Jul  :: mysql-server- Keepalived_healthcheckers[]: Opening file '/etc/keepalived/keepalived.conf'.

Jul  :: mysql-server- Keepalived_healthcheckers[]: Configuration is using :  Bytes

Jul  :: mysql-server- Keepalived_vrrp[]: Opening file '/etc/keepalived/keepalived.conf'.

Jul  :: mysql-server- Keepalived_vrrp[]: Configuration is using :  Bytes

Jul  :: mysql-server- Keepalived_vrrp[]: Using LinkWatch kernel netlink reflector...

Jul  :: mysql-server- Keepalived_healthcheckers[]: Using LinkWatch kernel netlink reflector...

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Entering BACKUP STATE

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP sockpool: [ifindex(), proto(), unicast(), fd(,)]

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Script(check_run) succeeded

可以看见VIP已经绑定在了master上，执行ip addr看看是否有这个VIP

[root@mysql-server- ~]# ip addr | grep eth1

: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu  qdisc pfifo_fast state UP qlen

    inet 192.168.0.100/ brd 192.168.0.255 scope global eth1

    inet 192.168.0.88/ scope global eth1

[root@mysql-server- ~]#

可以看见vip也已经绑定成功。

现在我们从远程机器登陆看看，使用vip，创建测试库，插入数据，最后模拟mysqld crash

[root@mysql-server-03 ~]# mysql -uadmin -p123456 -h 192.168.0.88 -P 14520

Warning: Using a password on the command line interface can be insecure.

Welcome to the MySQL monitor.  Commands end with ; or \g.

Your MySQL connection id is 47

Server version: 5.6.19-log MySQL Community Server (GPL)

Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective

owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> create database dengyayun;

Query OK, 1 row affected (0.01 sec)

mysql> use dengyayun

Database changed

mysql> create table t1 ( id int);

Query OK, 0 rows affected (0.38 sec)

mysql> insert into t1 select 999;

Query OK, 1 row affected (0.03 sec)

Records: 1  Duplicates: 0  Warnings: 0

mysql>

发现使用vip登陆没有问题，创建库以及插入数据都木有问题。现在杀掉mysqld进程，看vip是否进行了漂移，以及查看数据是否存在。

[root@mysql-server- ~]# pkill - mysqld

过了一会儿，报警邮件就到了，以及vip也已经切换了。如下：

查看slave上面的message信息，如下输出：

[root@mysql-server- ~]# tail -n  /var/log/messages

Jul  :: mysql-server- Keepalived_healthcheckers[]: Registering Kernel netlink command channel

Jul  :: mysql-server- Keepalived_vrrp[]: Opening file '/etc/keepalived/keepalived.conf'.

Jul  :: mysql-server- Keepalived_vrrp[]: Configuration is using :  Bytes

Jul  :: mysql-server- Keepalived_vrrp[]: Using LinkWatch kernel netlink reflector...

Jul  :: mysql-server- Keepalived_healthcheckers[]: Opening file '/etc/keepalived/keepalived.conf'.

Jul  :: mysql-server- Keepalived_healthcheckers[]: Configuration is using :  Bytes

Jul  :: mysql-server- Keepalived_healthcheckers[]: Using LinkWatch kernel netlink reflector...

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Entering BACKUP STATE

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP sockpool: [ifindex(), proto(), unicast(), fd(,)]

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Script(check_run) succeeded

Jul  :: mysql-server- dhclient[]: DHCPREQUEST on eth0 to 192.168.87.254 port  (xid=0x4ada08db)

Jul  :: mysql-server- dhclient[]: DHCPACK from 192.168.87.254 (xid=0x4ada08db)

Jul  :: mysql-server- dhclient[]: bound to 192.168.87.135 -- renewal in  seconds.

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Transition to MASTER STATE

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Group(VG1) Syncing instances to MASTER state

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Entering MASTER STATE

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) setting protocol VIPs.

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.0.88

Jul  :: mysql-server- Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.0.88 added

Jul  :: mysql-server- Keepalived_vrrp[]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.0.88

[root@mysql-server- ~]#

最后我们再次使用vip登陆；发现数据没有异常。复制也停止了，因为已经切换为主库。

[root@mysql-server-03 ~]# mysql -uadmin -p123456 -h 192.168.0.88 -P14521

Warning: Using a password on the command line interface can be insecure.

Welcome to the MySQL monitor.  Commands end with ; or \g.

Your MySQL connection id is 301

Server version: 5.6.19-log MySQL Community Server (GPL)

Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective

owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> select * from dengyayun.t1;

+------+

| id   |

+------+

|  999 |

+------+

1 row in set (0.00 sec)

mysql> pager cat | egrep 'IO_Running|SQL_Running'

PAGER set to 'cat | egrep 'IO_Running|SQL_Running''

mysql> show slave status\G

             Slave_IO_Running: No

            Slave_SQL_Running: No

      Slave_SQL_Running_State:

1 row in set (0.00 sec)

mysql>

Keepalived+MySQL实现高可用的更多相关文章

  1. 利用Keepalived+mysql构建高可用MySQL双主自动切转

    转载:http://www.it300.com/index.php/article-15266.html 关于MySQL-HA,目前有多种解决方案,比如heartbeat.drbd.mmm.共享存储, ...

  2. Ubuntu编译安装HAprox+Keepalived+MySQL负载高可用架构(结合Docker容器配置)

    系统环境:Ubuntu16.04(Docker容器) 架构环境: Keepalived/HAproxy MASTER: 172.17.0.4 Keepalived/HAproxy BACKUP: 17 ...

  3. Keepalived+MySQL实现高可用(转)

    http://www.cnblogs.com/wingsless/p/4033093.html   MHA高可用 http://www.cnblogs.com/gomysql/p/3856484.ht ...

  4. 基于keepalived搭建MySQL的高可用集群

    MySQL的高可用方案一般有如下几种: keepalived+双主,MHA,MMM,Heartbeat+DRBD,PXC,Galera Cluster 比较常用的是keepalived+双主,MHA和 ...

  5. (转)基于keepalived搭建MySQL的高可用集群

    基于keepalived搭建MySQL的高可用集群  原文:http://www.cnblogs.com/ivictor/p/5522383.html MySQL的高可用方案一般有如下几种: keep ...

  6. LVS+Keepalived搭建MyCAT高可用负载均衡集群

    LVS+Keepalived 介绍 LVS LVS是Linux Virtual Server的简写,意即Linux虚拟服务器,是一个虚拟的服务器集群系统.本项目在1998年5月由章文嵩博士成立,是中国 ...

  7. MariaDB+Keepalived双主高可用配置MySQL-HA

    利用keepalived构建高可用MySQL-HA,保证两台MySQL数据的一致性,然后用keepalived实现虚拟VIP,通过keepalived自带的服务监控功能来实现MySQL故障时自动切换. ...

  8. 分布式数据存储 - MySQL主从复制高可用方案

    前面几篇文章说道MySQL数据库的高可用方案主从复制.主从复制的延迟产生原因.延迟检测及延迟解决方案(并未从根本上解决),这种主从复制方案保证数据的冗余的同时可以做读写分离来分担系统压力但是并非是高可 ...

  9. 技术实战：基于 MHA 方式实现 MySQL 的高可用(转)

    转自:http://os.51cto.com/art/201307/401702_all.htm MHA故障转移可以很好的帮我们解决从库数据的一致性问题,同时最大化挽回故障发生后的数据.本文分享了基于 ...

随机推荐

  1. requests模块的使用

    requests模块 什么是request模块:requests是python原生一个基于网络请求的模块,模拟浏览器发起请求. requests-get请求 # get请求 import reques ...

  2. Python全栈之路---数据类型—字符串

    字符串:有序的字符的集合,用于存储和表示基本的文本信息,一对单.双.或三引号中间包含的内容称之为字符串 1.特性:有序,不可变(开辟新地址存储字符串,python解释器会定期清空不用了的已存储的) & ...

  3. sql 50题

    /* Navicat MySQL Data Transfer Source Server : localhost Source Server Version : 50717 Source Host : ...

  4. iuplua test on luaforwindows

    SW https://github.com/rjpcomputing/luaforwindows/releases Steps Install lua for windows write a bat ...

  5. spring aop无法拦截类内部的方法调用

    1.概念 拦截器的实现原理就是动态代理,实现AOP机制.Spring 的代理实现有两种:一是基于 JDK Dynamic Proxy 技术而实现的:二是基于 CGLIB 技术而实现的.如果目标对象实现 ...

  6. Firebug 没死，活在 Firefox DevTools 中

    伯乐在线转注:2016年12月7日有一条<Firebug 宣布停止开发更新>的资讯,不少朋友误认为以后用不到 Firebug 了.其实在 2015 年 Firebug 已经在着手整合到 F ...

  7. SpringBoot RestFul风格API接口开发

    本文介绍在使用springBoot如何进行Restful Api接口的开发及相关注解已经参数传递如何处理. 一.概念: REST全称是Representational State Transfer,中 ...

  8. 关于DDR3控制器的使用

    关于DDR3控制器的使用 mig_7series_0 u_mig_7series_0 ( // Memory interface ports .ddr3_addr (ddr3_addr), // ou ...

  9. <ROS> 机器人描述--URDF和XACRO

    文章转自 https://blog.csdn.net/sunbibei/article/details/52297524 特此鸣谢原创作者的辛勤付出 1 URDF 文件 1.1 link和joint ...

  10. JVM学习总结（一）：Java内存区域

    一.JVM运行时数据区 1.程序计数器: (1)一块较小的线程私有的内存空间. (2)JVM的多线程是通过线程轮流切换并分配处理器执行时间的方式来实现的,在任何一个确定的时刻,一个处理器(或一个内核) ...