Mysql-MMM實現(Mysql雙主多從高可用)

一．mysql-mmm實現mysql 高可用架構
     MMM 即Master-Master Replication Manager for MySQL（mysql 主主複製管理器）關於 mysql
     主主複製配置的監控、故障轉移和管理的一套可伸縮的腳本套件（在任什麼時候候只有一個
節點能夠被寫入），這個套件也能對居於標準的主從配置的任意數量的從服務器進行讀
負載均衡，因此你能夠用它來在一組居於複製的服務器啓動虛擬 ip，除此以外，它還
有實現數據備份、節點之間從新同步功能的腳本。
     MySQL 自己沒有提供 replication failover 的解決方案，經過 MMM 方案能實現服務器的故障轉移，從而實現 mysql 的高可用。MMM 項目來自 Google：http://code.google.com/p/mysql-master-master
官方網站爲：http://mysql-mmm.org
mysql-mmm     主要功能由下面三個腳本提供
mmm_mond     負責全部的監控工做的監控守護進程，決定節點的移除等等
mmm_agentd   運行在 mysql 服務器上的代理守護進程，經過簡單遠程服務集提供給監控節點
mmm_control   經過命令行管理 mmm_mond 進程
     mysql-mmm 的監管端會提供多個虛擬 IP（VIP），包括一個可寫 VIP，多個可讀 VIP，經過監管的管理，這些 IP 會綁定在可用 mysql 之上，當某一臺 mysql 宕機時，監管會將 VIP
遷移至其餘 mysql。
    在整個監管過程當中，須要在 mysql 中添加相關受權用戶，以便讓 mysql 能夠支持監理機的維護。受權的用戶包括一個 mmm_monitor 用戶和一個 mmm_agent 用戶，若是想使用 mmm的備份工具則還要添加一個 mmm_tools 用戶。

部署開始，因爲機器資源有限，這裏的實驗，slave 就用一臺了。

二．部署的前期工做
1．環境描述
vmvare 虛擬機：4 臺
系統版本：CentOS release 6.6 (Final)  2.6.32-504.el6.x86_64
mysql版本：5.5.32
mysql-mmm版本：

4臺虛擬機信息：
MMM管理機:192.168.0.149  Monitor      test-A
master1:192.168.0.150    server-id=1  test-B
master2:192.168.0.160    server-id=3  test-D
slave:192.168.0.151      server-id=2  test-C

虛擬IP：
10.0.0.13   write
10.0.0.14   read
10.0.0.15   read
10.0.0.16   read

Mysql-MMM 架構配置簡介:
1.master1, master2 兩臺安裝 mysql,並作主主的配置
2.slave1 上安裝 mysql,並配置做爲 master1 的從服務器。
3.master1/2, slave1,Monitor 這四臺都要安裝 mysql-mmm,並配置：mmm_common.conf、
mmm_agent.conf 以及 mmm_mon.conf 文件

3、配置 mysql-master-1/2（主主同步),mysql-master-1 與 mysql-slave（主從同步）
注：全部的mysql都是新安裝的，因此沒有任何數據，環境相同。
1.一、 改my.cnf而後重啓服務
mysql-master-1:
[mysqld]
server-id       = 1
log-bin=mysql-bin
log-slave-updates  
auto_increment_offset=1  
auto_increment_increment=2

mysql-master-2:
[mysqld]
server-id       = 3
log-bin=mysql-bin
log-bin=mysql-bin
log-slave-updates  
auto_increment_offset=2  
auto_increment_increment=2

1.二、 配置master1和master2 作主主同步
master1 和 master2 都須要建立連接用戶
mysql> grant replication slave on *.* to 'rep'@'192.168.0.%' identified by
'test123';
Query OK, 0 rows affected (0.02 sec)

master1操做：
mysql> show master status;
+------------------+----------+--------------+---------------------------------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB                            |
+------------------+----------+--------------+---------------------------------------------+
| mysql-bin.000006 |      107 |              | mysql,performance_schema,information_schema |
+------------------+----------+--------------+---------------------------------------------+
1 row in set (0.00 sec)
 
master2操做：
mysql>  change master to
     >  master_host='192.168.0.150',
     >  master_port=3306,
     >  master_user='rep',
     >  master_password='test123',
     >  master_log_file='mysql-bin.000006',
     >  master_log_pos=107;
mysql> start slave;
mysql> show slave status\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.0.150
                  Master_User: rep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000006
          Read_Master_Log_Pos: 107
               Relay_Log_File: test-D-relay-bin.000006
                Relay_Log_Pos: 253
        Relay_Master_Log_File: mysql-bin.000006
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_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: 107
              Relay_Log_Space: 410
              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
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 1
1 row in set (0.00 sec)

ERROR:
No query specified

mysql> grant replication slave on *.* to 'rep'@'192.168.0.%' identified by 'test123';
mysql> show master status;                                  +------------------+----------+--------------+------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------------------+----------+--------------+------------------+
| mysql-bin.000003 |      107 |              |                  |
+------------------+----------+--------------+------------------+
1 row in set (0.00 sec)

master1操做：
mysql>  change master to
     >  master_host='192.168.0.160',
     >  master_port=3306,
     >  master_user='rep',
     >  master_password='test123',
     >  master_log_file='mysql-bin.000003',
     >  master_log_pos=107;
mysql> start slave;
mysql> show slave status\G;

2.一、 slave修改my.cnf並重啓服務
vi /data/3307/my.cnf
[mysqld]
server-id = 2
[root@test-C ~]# mysqladmin -uroot -p456 shutdown -S /data/3307/mysql.sock
[root@test-C ~]# /application/mysql/bin/mysqld_safe --defaults-file=/data/3307/my.cnf &
注：從上我用的是多實例

2.二、  配置同步參數
查看 master1 主庫的記錄點信息
flush tables with read lock;     #鎖表
mysql> show master status;
+------------------+----------+--------------+---------------------------------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB                            |
+------------------+----------+--------------+---------------------------------------------+
| mysql-bin.000006 |      107 |              | mysql,performance_schema,information_schema |
+------------------+----------+--------------+---------------------------------------------+
1 row in set (0.00 sec)
mysqldump -uroot --event -A -B >/tmp/master1.sql   # 備份主庫
unlock tables;   #解鎖

slave 從庫進行操做:
mysql -uroot <master1.sql -S /data/3307/mysql.sock
mysql> CHANGE MASTER TO   
    -> MASTER_HOST='192.168.0.150',
    -> MASTER_PORT=3306,  
    -> MASTER_USER='rep',  
    -> MASTER_PASSWORD='test123',
    -> MASTER_LOG_FILE='mysql-bin.000006',
    -> MASTER_LOG_POS=107;
Query OK, 0 rows affected (0.04 sec)
 
mysql> start slave;
Query OK, 0 rows affected (0.02 sec)
 
mysql> show slave status\G;

 
4、配置mysql-mmm
4.一、 安裝mysql-mmm
注：須要在這四臺 server 上都安裝 mysql-mmm
CentOS 軟件倉庫默認是不含這些軟件的，必需要有epel這個包的支持。因此咱們必須先安裝epel。
四臺同時操做:
cd tools
wget http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
rpm -Uvh epel-release-6-8.noarch.rpm  
yum install -y mysql-mmm*

 
4.二、 配置mmm代理和監控帳號的權限
如今環境已經配置好，我沒有配置忽略 mysql庫和 user表，因此只要在任意一臺主庫上執
行下面的操做，其餘的庫就都有這倆帳號了。
mysql> GRANT REPLICATION CLIENT ON *.* TO 'mmm_monitor'@'192.168.0.%' IDENTIFIED  BY 'test123';
mysql> GRANT SUPER, REPLICATION CLIENT, PROCESS ON *.* TO 'mmm_agent'@'192.168.0.%' IDENTIFIED BY 'test123';       
Query OK, 0 rows affected (0.00 sec)
mysql> flush privileges;
Query OK, 0 rows affected (0.06 sec)
注：master一、master二、slave 是同樣的
mysql> select user,host from mysql.user;
+-------------+-------------+
| user        | host        |
+-------------+-------------+
| root        | 127.0.0.1   |
| mmm_agent   | 192.168.0.% |
| mmm_monitor | 192.168.0.% |
| rep         | 192.168.0.% |
| root        | ::1         |
|             | localhost   |
| root        | localhost   |
|             | test-B      |
| root        | test-B      |
+-------------+-------------+
8 rows in set (0.00 sec)
      
 
4.三、 全部服務器均需配置/etc/mysql-mmm/mmm_common.conf
vi /etc/mysql-mmm/mmm_common.conf     
active_master_role      writer

<host default>
    cluster_interface       eth0
    pid_path                /var/run/mysql-mmm/mmm_agentd.pi
d
    bin_path                /usr/libexec/mysql-mmm/
    replication_user        rep
    replication_password    test123
    agent_user              mmm_agent
    agent_password          test123
</host>

<host db1>
    ip      192.168.0.150
    mode    master
    peer    db2
</host>

<host db2>
    ip      192.168.0.160
    mode    master
    peer    db1
</host>

<host db3>
    ip      192.168.0.151
    mode    slave
</host>

<role writer>
    hosts   db1, db2
    ips     10.0.0.13
    mode    exclusive
</role>

<role reader>
    hosts   db1, db2, db3
    ips     10.0.0.14, 10.0.0.15, 10.0.0.16
    mode    balanced
</role>

 
4.四、數據庫主機配置/etc/mysql-mmm/mmm_agent.conf
hostname      ip  my.cnf -serverid  dbname
master1  192.168.0.150      1         db1
master2  192.168.0.160      3         db2
slave1   192.168.0.151      2         db3
根據上表對三臺 mysql服務器的/etc/mysql-mmm/mmm_agent.conf 配置文件進行修改
例：
[root@mysql-mmm-master1 tools]# vi /etc/mysql-mmm/mmm_agent.conf
include mmm_common.conf
# The 'this' variable refers to this server.  Proper operation requires
# that 'this' server (db1 by default), as well as all other servers, have the
# proper IP addresses set in mmm_common.conf.
this db1
 
4.五、 monitor主機配置/etc/mysql-mmm/mmm_mon.conf
include mmm_common.conf

<monitor>
    ip                  127.0.0.1
    pid_path            /var/run/mysql-mmm/mmm_mond.pid
    bin_path            /usr/libexec/mysql-mmm
    status_path         /var/lib/mysql-mmm/mmm_mond.status
    ping_ips            192.168.0.150, 192.168.0.151, 192.16
8.0.160
    auto_set_online     30

    # The kill_host_bin does not exist by default, though th
e monitor will
    # throw a warning about it missing.  See the section 5.1
0 "Kill Host
    # Functionality" in the PDF documentation.
    #
    # kill_host_bin     /usr/libexec/mysql-mmm/monitor/kill_
host
    #
</monitor>

<host default>
    monitor_user        mmm_monitor
    monitor_password    test123
</host>

debug 0

4.六、 啓動mysql-mmm
master-1,master-2,slave 啓動代理：
編輯/etc/default/mysql-mmm-agent 來開啓
[root@mysql-mmm-master2 tools]# vi /etc/default/mysql-mmm-agent
# mysql-mmm-agent defaults
ENABLED=1
全部數據庫主機啓動 mmm-agent:
/etc/init.d/mysql-mmm-agent start
monitor 主機啓動 mmm-monitor
/etc/init.d/mysql-mmm-monitor start
 
4.七、 mmm_control命令監控mysql 服務器狀態
[root@mysql-mmm-monitor ~]# mmm_control show
  db1(192.168.0.150) master/ONLINE. Roles: reader(10.0.0.15), writer(10.0.0.13)
  db2(192.168.0.160) master/ONLINE. Roles: reader(10.0.0.14)
  db3(192.168.0.151) slave/ONLINE. Roles: reader(10.0.0.16)

 
4.八、 測試兩個mysql服務器可否實現故障自動切換
將db1的mysql服務中止
[root@test-B ~]# /etc/init.d/mysqld stop
Shutting down MySQL. SUCCESS!
等待30秒在 mysql-mmm-monitor 服務器上進行監控查看
[root@test-A ~]# mmm_control show
  db1(192.168.0.150) master/HARD_OFFLINE. Roles:
  db2(192.168.0.160) master/ONLINE. Roles: reader(10.0.0.14), writer(10.0.0.13)
  db3(192.168.0.151) slave/ONLINE. Roles: reader(10.0.0.15), reader(10.0.0.16)

slave檢查master_host 是否切換到了另外一個主庫地址：
[root@test-C ~]# mysql -uroot -p -e "show slave status\G" -S /data/3307/mysql.sock                    
Enter password:
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.0.160
                  Master_User: rep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000003
          Read_Master_Log_Pos: 537
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 253
        Relay_Master_Log_File: mysql-bin.000003
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_Ignore_DB: mysql
           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: 537
              Relay_Log_Space: 403
              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
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 3

恢復master-1(db1)
[root@test-B ~]# /etc/init.d/mysqld start
Starting MySQL.. SUCCESS!
monitor端檢查恢復狀況
[root@test-A ~]# mmm_control show
  db1(192.168.0.150) master/ONLINE. Roles: reader(10.0.0.16)
  db2(192.168.0.160) master/ONLINE. Roles: reader(10.0.0.14), writer(10.0.0.13)
  db3(192.168.0.151) slave/ONLINE. Roles: reader(10.0.0.15)
能夠看到當 db1 恢復後就充當 slave 的角色了！只有當 db2 掛了之後db1 又會擔當起主服務器的寫入功能。

4.九、 mmm_control命令介紹
Valid commands are:
    help                              - show this message
    ping                              - ping monitor
    show                              - show status
    checks [<host>|all [<check>|all]] - show checks status
    set_online <host>                 - set host <host> online
    set_offline <host>                - set host <host> offline
    mode                              - print current mode.
    set_active                        - switch into active mode.
    set_manual                        - switch into manual mode.
    set_passive                       - switch into passive mode.
    move_role [--force] <role> <host> - move exclusive role <role> to host <host>
                                        (Only use --force if you know what you are doing!)
    set_ip <ip> <host>                - set role with ip <ip> to host <host>

5、配置過程當中我遇到的一些問題和解決方法
問題：
配置過程當中，到最後查看全部服務器狀態，從服務器不在狀態：
[root@test-A ~]# mmm_control show
[root@test-A ~]# mmm_control show
  db1(192.168.0.150) master/ONLINE. Roles: reader(10.0.0.15), writer(10.0.0.13)
  db2(192.168.0.160) master/ONLINE. Roles: reader(10.0.0.14), reader(10.0.0.16)
  db3(192.168.0.151) slave/HARD_OFFLINE. Roles:
如上，解決方法：
    從服務器上的mysql，原來作測試時，用的多實例，mysql服務端口爲3307。停掉從服務器上的主從，而後在配置文件中把端口改成3306，重啓服務。從新作一下主從同步後，從新啓動MMM的代理服務後，再次在MMM管理端查看全部服務器狀態，已所有正常，以下：
[root@test-A ~]# mmm_control show                    
  db1(192.168.0.150) master/ONLINE. Roles: reader(10.0.0.15), writer(10.0.0.13)
  db2(192.168.0.160) master/ONLINE. Roles: reader(10.0.0.14)
  db3(192.168.0.151) slave/ONLINE. Roles: reader(10.0.0.16)