日期:2014-05-16  浏览次数:20665 次

使用keepalived构建高可用mysql-HA
使用keepalived构建高可用mysql-HA

关于mysql-HA,目前有多种解决方案,比如heartbeat、drbd、mmm、共享存储,但是它们各有优缺点。heartbeat、drbd配置较为复杂,需要自己写脚本才能实现mysql自动切换,对于不会脚本语言的人来说,这无疑是一种脑裂问题;对于mmm,生产环境中很少有人用,且mmm 管理端需要单独运行一台服务器上,要是想实现高可用,就得对mmm管理端做HA,这样无疑又增加了硬件开支;对于共享存储,个人觉得mysql数据还是放在本地较为安全,存储设备毕竟存在单点隐患。使用mysql双master+keepalived是一种非常好的解决方案,在mysql-HA环境中,mysql互为主从关系,这样就保证了两台mysql数据的一致性,然后用keepalived实现虚拟IP,通过keepalived自带的服务监控功能来实现mysql故障时自动切换

下面,我把即将上线的一个生产环境中的架构与大家分享一下,看一下这个架构中,mysql-HA是如何实现的,环境拓扑如下


Mysql-VIP:192.168.1.200

Mysql-master1:192.168.1.201

Mysql-master2:192.168.1.202


OS版本:CentOS 5.4

Mysql版本:5.0.89

Keepalived版本:1.1.20



一、mysqlmaster-master配置

1、修改mysql配置文件

两台mysql均如要开启binlog日志功能,开启方法:在mysql配置文件[mysqld]段中加上log-bin=mysql-bin选项

两台mysql的server-ID不能一样,默认情况下两台mysql的serverID都是1,需将其中一台修改为2即可

2、将192.168.1.201设为192.168.1.202的主服务器

在192.168.1.201上新建授权用户

mysql> grant replication slave on *.* to'replication'@'%' identified by 'replication';

Query OK, 0 rows affected (0.00 sec)

mysql> show master status;

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

| File
|Position | Binlog_Do_DB | Binlog_Ignore_DB |

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

| mysql-bin.000003 |

374 |
|
|

+------------------+----------+--------------+------------------+
1 row in set (0.00 sec)



在192.168.1.202上将192.168.1.201设为自己的主服务器

mysql> change master to master_host='192.168.1.201',master_user='replication',master_password='replication',master_log_file='mysql-bin.000003',master_log_pos=374;

Query OK, 0 rows affected (0.05 sec)

mysql> start slave;

Query OK, 0 rows affected (0.00 sec)

mysql> show slave status\G

*************************** 1. row***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.1.201
Master_User: replication
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000003
Read_Master_Log_Pos: 374
Relay_Log_File: mysql-master2-relay-bin.000002
Relay_Log_Pos: 235
Relay_Master_Log_File: mysql-bin.000003
Slave_IO_Running:Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replcate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:

Replicate_Wild_Ignore_Table:
Last_Errno:0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 374
Relay_Log_Space: 235
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed:No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 0
1 row in set (0.00 sec)



3、将192.168.1.202设为192.168.1.201的主服务器

在192.168.1.202上新建授权用户

mysql> grant replication slave on *.* to'replication'@'%' identified by 'replication';

mysql> show master status;

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

| File

| Position | Binlog_Do_DB |Binlog_Ignore_DB |

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

| mysql-bin.000003 |
374 |
|
|

+------------------+----------+--------------+------------------+
1 row in set (0.00 sec)

在192.168.1.201上,将192.168.1.202设为自己的主服务器

mysql> change master tomaster_host='192.168.1.202',master_user='replication',master_password='replication',master_log_file='mysql-bin.000003',master_log_pos=374;

Query OK, 0 rows affected (0.05 sec)

mysql> start slave;