|
2、192.168.1.202上keepalived安装及配置
安装keepalived #tar zxvf keepalived-1.1.20.tar.gz #cd keepalived-1.1.20 #./configure --prefix=/usr/local/keepalived--with-kernel-dir=/usr/src/kernels/2.6.18-164.el5-i686 #make && make install
配置keepalived 这台配置和上面基本一样，但有三个地方不同：优先级为90、无抢占设置、real_server为本机IP #mkdir /etc/keepalived #vi /etc/keepalived/keepalived.conf | ! Configuration File for keepalived global_defs {
notification_email {
luwenju@live.cn
}
notification_email_from luwenju@live.cn
smtp_server 127.0.0.1
smtp_connect_timeout 30
router_id mysql-ha
}
vrrp_instance VI_1 {
state BACKUP
interface eth0
virtual_router_id 51
priority 90
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
192.168.1.200
}
}
virtual_server 192.168.1.200 3306 {
delay_loop 2
lb_algo wrr
lb_kind DR
persistence_timeout 60
protocol TCP
real_server 192.168.1.202 3306 {
weight 3
notify_down /usr/local/mysql/bin/mysql.sh
TCP_CHECK {
connect_timeout 10
nb_get_retry 3
delay_before_retry 3
connect_port 3306
}
}
|
编写检测服务down后所要执行的脚本
#vi /usr/local/mysql/bin/mysql.sh | #!/bin/sh pkill keepalived |
#chmod +x /usr/local/mysql/bin/mysql.sh
启动keepalived #/usr/local/keepalived/sbin/keepalived –D #ps -aux | grep keepalived
测试
●停止mysql服务，看keepalived健康检查程序是否会触发我们编写的脚本
三、测试
●MySQL远程登录测试
我们找一台安装有mysql客户端的windows，然后登录VIP，看是否能登录，在登录之两台mysql服务器都要授权允许从远程登录
| mysql> grant all privileges on *.* to 'root'@'%' identified by '123456'; Query OK, 0 rows affected (0.00 sec)
mysql> flush privileges; Query OK, 0 rows affected (0.00 sec)
|
使用客户端登录VIP测试
| C:\mysql\bin>mysql.exe -uroot -p123456 -h192.168.1.200 -P3306 Welcome to the MySQL monitor.
Commands end with ; or \g. Your MySQL connection id is 224 Server version: 5.0.89-log Source distribution
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> |
●
keepalived故障转移测试
※在windows客户端一直去ping
VIP，然后关闭192.168.1.201上的keepalived，正常情况下VIP就会切换到192.168.1.202上面去
※开启192.168.1.201上的keepalived，关闭192.168.1.202上的keepalived，看是否能自动切换，正常情况下VIP又会属于192.168.1.201 注：keepalived切换速度还是非常块的，整个切换过程只需1-3秒
●
mysql故障转移测试
※在192.168.1.201上关闭mysql服务，看VIP是否会切换到192.168.1.202上
※开启192.168.1.201上的mysql和keepalived，然后关闭192.168.1.202上的mysql，看VIP是否会切换到192.168.1.201上
下面是用windows客户端连接的mysql的VIP，在切换时我执行了一个mysql查询命令，从执行show databases到显示出结果时间为3-5秒（大家可以看到上面有个错误提示，不过不用担心，因为我们的keepalived切换大概为3秒左右，这3秒左右VIP是谁都不属于的）
| mysql> show databases; ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id:
592 Current database: *** NONE ***
+--------------------+ | Database
| +--------------------+ | information_schema | | mysql
| | test
| +--------------------+ 3 rows in set (9.01 sec)
|
后话：世间万事万物，都不具备绝对的完美，就像上面的mysql-HA一样，keepalived只能做到对3306的健康检查，但是做不到比如像mysql复制中的slave-SQL、slave-IO进程的检查。所以要想做到一些细致的健康检查，还得需要借助额外的监控工具，比如nagios，然后用nagios实现短信、邮件报警，从而能够有效地解决问题。
| 
免费注册
发表于 2010-11-29 18:01
]
[/fly]
