溫馨提示×

您好，登錄后才能下訂單哦！

密碼登錄×
登錄注冊(cè)×
其他方式登錄
點(diǎn)擊 登錄注冊(cè) 即表示同意《億速云用戶服務(wù)條款》

MySQL中HA MHA如何搭建

發(fā)布時(shí)間：2021-11-16 15:54:48 來源：億速云 閱讀：131 作者：小新 欄目：MySQL數(shù)據(jù)庫(kù)

小編給大家分享一下MySQL中HA MHA如何搭建，相信大部分人都還不怎么了解，因此分享這篇文章給大家參考一下，希望大家閱讀完這篇文章后大有收獲，下面讓我們一起去了解一下吧！

mha結(jié)構(gòu)恢復(fù)過程：
MySQL中HA MHA如何搭建

mha架構(gòu)圖：
MySQL中HA MHA如何搭建



本次測(cè)試環(huán)境為3臺(tái)服務(wù)器
其中將一臺(tái)slave作為mha中的manager節(jié)點(diǎn)

  1. --------------------------------------

  2. ip             hostname      mysql

  3. --------------------------------------

  4. 10.1.10.244    data01        master

  5. 10.1.10.80     data02        slave

  6. 10.1.10.91     manager       slave

  7. --------------------------------------



主機(jī)情況：

服務(wù)器發(fā)行版：centos6.7
內(nèi)核：2.6.32-220.el6.x86_64
數(shù)據(jù)庫(kù)軟件版本：MySQL Community 5.6.29




------------------------------------- 修改主機(jī)名 -------------------------------------

undefined
244(master):

  1. # vi /etc/sysconfig/network

將HOSTNAME修改為 data01

80(slave):

  1. # vi /etc/sysconfig/network

將HOSTNAME修改為 data02

91(slave):

  1. # vi /etc/sysconfig/network

將HOSTNAME修改為 manager


同時(shí)修改三臺(tái)服務(wù)器hosts：

  1. # vi /etc/hosts

添加：
10.1.10.244 data01
10.1.10.80 data02
10.1.10.91 manager



------------------------------------- 建立互信關(guān)系 ------------------------------------- 

在三臺(tái)服務(wù)器上分別執(zhí)行：
244(master)、80(slave)、91(slave):

  1. # cd /root/.ssh

  2. # ssh-keygen -t rsa

全部默認(rèn)，直接回車


在224(master)上執(zhí)行:

  1. # cd /root/.ssh

  2. # cat id_dsa.pub >> authorized_keys

  3. # scp root@10.1.10.80:/root/.ssh/id_dsa.pub ./id_dsa.pub.data02.80

  4. # scp root@10.1.10.91:/root/.ssh/id_dsa.pub ./id_dsa.pub.manager.91


  6. # cat id_dsa.pub.data02.80 >> authorized_keys

  7. # cat id_dsa.pub.manager.91 >> authorized_keys


  9. # scp authorized_keys root@10.1.10.80:/root/.ssh/authorized_keys

  10. # scp authorized_keys root@10.1.10.91:/root/.ssh/authorized_keys



從244(master)開始兩兩驗(yàn)證：
[root@data01 ~]# ssh data02
……略……
[root@data02 ~]# ssh manager
……略……
[root@manager ~]# ssh data01
……略……
[root@data01 ~]# ssh manager
……略……
[root@manager ~]# ssh data02
……略……
[root@data02 ~]# ssh data01
……略……



------------------------------------- 建立主從關(guān)系 ------------------------------------- 

在三臺(tái)服務(wù)器上的mysql-server上分別執(zhí)行：
244(master)、80(slave)、91(slave):

  1. mysql> GRANT super, replication slave, reload ON *.* TO repl_user@'10.1.10.%' IDENTIFIED BY 'repl_user';

  2. Query OK, 0 rows affected (0.00 sec)


  4. mysql> FLUSH PRIVILEGES;

  5. Query OK, 0 rows affected (0.00 sec)



分別修改三臺(tái)服務(wù)器上mysql的配置文件：
244(master):

  1. [mysqld]

  2. log-bin         = /var/lib/mysql/data01-bin

  3. log-bin-index   = /var/lib/mysql/data01-bin.index


  5. server-id       = 244


  7. relay-log       = /var/lib/mysql/data01-relay-bin

  8. relay-log-index = /var/lib/mysql/data01-relay-bin.index

  9. log-slave-updates


80(slave):

  1. [mysqld]

  2. log-bin         = /var/lib/mysql/data02-bin

  3. log-bin-index   = /var/lib/mysql/data02-bin.index


  5. server-id       = 80


  7. relay-log       = /var/lib/mysql/data02-relay-bin

  8. relay-log-index = /var/lib/mysql/data02-relay-bin.index

  9. log-slave-updates


91(slave):

  1. [mysqld]

  2. log-bin         = /var/lib/mysql/manager-bin

  3. log-bin-index   = /var/lib/mysql/manager-bin.index


  5. server-id       = 91


  7. relay-log       = /var/lib/mysql/manager-relay-bin

  8. relay-log-index = /var/lib/mysql/manager-relay-bin.index

  9. log-slave-updates


在兩臺(tái)slave上分別執(zhí)行：
80(slave)、91(slave):

  1. mysql> CHANGE MASTER TO

  2.     -> MASTER_HOST = '10.1.10.244',

  3.     -> MASTER_PORT = 3306,

  4.     -> MASTER_USER = 'repl_user',

  5.     -> MASTER_PASSWORD = 'repl_user';

  6. Query OK, 0 rows affected, 2 warnings (0.03 sec)


  8. mysql> START SLAVE;

  9. Query OK, 0 rows affected (0.00 sec)

執(zhí)行完后可以查看一下復(fù)制進(jìn)程是否出問題：

  1. mysql> SHOW SLAVE STATUS\G


若顯示IO和SQL線程為Yes則表示復(fù)制建立好了：

Slave_IO_Running: Yes
Slave_SQL_Running: Yes

也可以通過SHOW PROCESSLIST來看。




------------------------------------- 安裝mha-manager及mha-node ------------------------------------- 

即將需要用到的附件：

mha4mysql-node-0.56.tar.gz
mha4mysql-manager-0.56.tar.gz

這兩個(gè)tar包可以搜一下


在三臺(tái)服務(wù)器上分別執(zhí)行：
244(data01)、80(data02)、91(manager):

  1. # yum install -y perl-DBD-MySQL



繼續(xù)分別在三臺(tái)服務(wù)器上安裝mha-node工具：
mha-node安裝：

  1. # tar zxvf mha4mysql-node-0.56.tar.gz

  2. # cd mha4mysql-node-0.56

  3. # perl Makefile.PL

  4. # make && make install



在管理服務(wù)器上安裝mha-manager工具：
91(manager):
先在manager服務(wù)器上安裝一些依賴工具或perl模塊：

  1. # yum install -y perl-Config-Tiny


以下三個(gè)可能安不上：

  1. # yum install -y perl-Log-Dispatch

  2. # yum install -y perl-Parallel-ForkManager

  3. # yum install -y perl-Config-IniFiles


可以通過perl CPAN來安裝，如果沒有，要先通過yum安裝一下CPAN：

  1. # yum install -y perl-CPAN



進(jìn)入CPAN來安裝perl模塊：

  1. # perl -MCPAN -e shell

  1. cpan[1]> install Log::Dispatch

  2. cpan[1]> install Parallel::ForkManager

  3. cpan[1]> install Config::IniFiles


如果安裝失敗，可以根據(jù)提示信息，先安裝一些依賴模塊，暫時(shí)總結(jié)如下（CPAN中）：

  1. install Test::Requires

  2. install Module::Runtime

  3. install Dist::CheckConflicts

  4. install Params::Validate

  5. install Module::Runtime

  6. install Module::Implementation

  7. install ExtUtils::MakeMaker



mha-manger安裝：

  1. # tar zxvf mha4mysql-manager-0.56.tar.gz

  2. # cd mha4mysql-manager-0.56

  3. # perl Makefile.PL


通過檢查Makefile.PL可以得知之前的模塊是否安裝成功。
檢查效果如下：
…………
[Core Features]
- DBI                   ...loaded. (1.609)
- DBD::mysql            ...loaded. (4.013)
- Time::HiRes           ...loaded. (1.9728)
- Config::Tiny          ...loaded. (2.12)
- Log::Dispatch         ...loaded. (2.54)
- Parallel::ForkManager ...loaded. (1.17)
- MHA::NodeConst        ...loaded. (0.56)
…………

如果missing則表示缺少。
如果都o(jì)k，則編譯：

  1. # make && make install




------------------------------------- 添加mha配置文件 -------------------------------------

在管理服務(wù)器上配置：
91(manager):

  1. # mkdir /var/log/mha

  2. # vi /etc/mha-manger.cnf


此次實(shí)驗(yàn)僅一個(gè)節(jié)點(diǎn)，若多個(gè)節(jié)點(diǎn)可以改一下manager服務(wù)器的配置文件結(jié)構(gòu)：
touch /etc/masterha_default.cnf 寫[server default]
touch /etc/node1.cnf 寫該節(jié)點(diǎn)上的server信息，如[server_1]、[server_2]等
分別用 --global_conf=/etc/masterha_default.cnf --conf=/etc/node1.cnf來使用

-------- 配置文件 --------

  1. [server default]

  2. manager_workdir         = /var/log/mha/

  3. manager_log             = /var/log/mha/manager.log


  5. ssh_user                = root

  6. repl_user               = repl_user

  7. repl_password           = repl_user


  9. [server_1]

  10. hostname                = 10.1.10.244

  11. user                    = root

  12. password                = root

  13. candidate_master        = 1

  14. master_binlog_dir       = /var/lib/mysql


  16. [server_2]

  17. hostname                = 10.1.10.80

  18. user                    = root

  19. password                = root

  20. #candidate_master       = 1

  21. master_binlog_dir       = /var/lib/mysql


  23. [server_3]

  24. hostname                = 10.1.10.91

  25. user                    = root

  26. password                = root

  27. #candidate_master       = 1

  28. master_binlog_dir       = /var/lib/mysql

其他參數(shù)此處取默認(rèn)值，更多參數(shù)可查閱本文結(jié)尾處的參考文檔。
-------- 配置文件 --------


undefined

  1. # masterha_check_ssh --conf=/etc/mha-manager.cnf


 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
 - [info] Reading application default configuration from /etc/mha-manager.cnf..
 - [info] Reading server configuration from /etc/mha-manager.cnf..
 - [info] Starting SSH connection tests..
 - [debug] 
 - [debug]  Connecting via SSH from root@10.1.10.244(10.1.10.244:22) to root@10.1.10.80(10.1.10.80:22)..
 - [debug]   ok.
 - [debug]  Connecting via SSH from root@10.1.10.244(10.1.10.244:22) to root@10.1.10.91(10.1.10.91:22)..
 - [debug]   ok.
 - [debug] 
 - [debug]  Connecting via SSH from root@10.1.10.80(10.1.10.80:22) to root@10.1.10.244(10.1.10.244:22)..
 - [debug]   ok.
 - [debug]  Connecting via SSH from root@10.1.10.80(10.1.10.80:22) to root@10.1.10.91(10.1.10.91:22)..
 - [debug]   ok.
 - [debug] 
 - [debug]  Connecting via SSH from root@10.1.10.91(10.1.10.91:22) to root@10.1.10.244(10.1.10.244:22)..
Warning: Permanently added '10.1.10.91' (RSA) to the list of known hosts.
 - [debug]   ok.
 - [debug]  Connecting via SSH from root@10.1.10.91(10.1.10.91:22) to root@10.1.10.80(10.1.10.80:22)..
 - [debug]   ok.
 - [info] All SSH connection tests passed successfully.


繼續(xù)檢查復(fù)制是否通：

  1. # masterha_check_repl --conf=/etc/mha-manager.cnf


若看到【MySQL Replication Health is OK.】則表示成功連通。

若失敗，則可以從防火墻，對(duì)應(yīng)mysql服務(wù)器用戶權(quán)限，對(duì)應(yīng)操作系統(tǒng)用戶對(duì)文件的讀寫權(quán)限等方面排查。


------------------------------------- 管理manager -------------------------------------

繼續(xù)在管理服務(wù)器上啟動(dòng)：
91(manager):
啟動(dòng)manager：

  1. # nohup masterha_manager --conf=/etc/mha-manager.cnf /var/log/mha/manager.log 2>&1 &


檢查進(jìn)程：

  1. # ps -ef | grep manager

root     18210 10044  0 18:11 pts/1    00:00:00 perl /usr/local/bin/masterha_manager --conf=/etc/mha-manager.cnf /var/log/mha/manager.log


可以看一下最后的日志情況：

  1. # tail -20 /var/log/mha/manager.log

……………………
Thu Feb 18 18:11:37 2016 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..


繼續(xù)檢查master狀態(tài)：

  1. # masterha_check_status --conf=/etc/mha-manager.cnf

mha-manager (pid:18210) is running(0:PING_OK), master:10.1.10.244


關(guān)閉manager：

  1. # masterha_stop  --conf=/etc/mha-manager.cnf

Stopped mha-manager successfully.


------------------------------------- failover檢測(cè) -------------------------------------

此處模擬服務(wù)器整個(gè)宕機(jī)

操作：直接重啟master服務(wù)器（此處是data01，即244）


通過tail -f查看mha-manager.log日志，刷出來如下記錄：

  1. Thu Feb 18 18:23:37 2016 - [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away)

  2. Thu Feb 18 18:23:37 2016 - [info] Executing SSH check script: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql --output_file=/var/tmp/save_binary_logs_test --manager_version=0.56 --binlog_prefix=data01-bin

  3. Thu Feb 18 18:23:37 2016 - [warning] HealthCheck: SSH to 10.1.10.244 is NOT reachable.

  4. Thu Feb 18 18:23:43 2016 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.1.10.244' (4))

  5. Thu Feb 18 18:23:43 2016 - [warning] Connection failed 2 time(s)..

  6. Thu Feb 18 18:23:46 2016 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.1.10.244' (4))

  7. Thu Feb 18 18:23:46 2016 - [warning] Connection failed 3 time(s)..

  8. Thu Feb 18 18:23:49 2016 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.1.10.244' (4))

  9. Thu Feb 18 18:23:49 2016 - [warning] Connection failed 4 time(s)..

  10. Thu Feb 18 18:23:49 2016 - [warning] Master is not reachable from health checker!

  11. Thu Feb 18 18:23:49 2016 - [warning] Master 10.1.10.244(10.1.10.244:3306) is not reachable!

  12. Thu Feb 18 18:23:49 2016 - [warning] SSH is NOT reachable.

  13. Thu Feb 18 18:23:49 2016 - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/mha-manager.cnf again, and trying to connect to all servers to check server status..

  14. Thu Feb 18 18:23:49 2016 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.

  15. Thu Feb 18 18:23:49 2016 - [info] Reading application default configuration from /etc/mha-manager.cnf..

  16. Thu Feb 18 18:23:49 2016 - [info] Reading server configuration from /etc/mha-manager.cnf..

  17. Thu Feb 18 18:23:50 2016 - [info] GTID failover mode = 0

  18. Thu Feb 18 18:23:50 2016 - [info] Dead Servers:

  19. Thu Feb 18 18:23:50 2016 - [info]   10.1.10.244(10.1.10.244:3306)

  20. Thu Feb 18 18:23:50 2016 - [info] Alive Servers:

  21. Thu Feb 18 18:23:50 2016 - [info]   10.1.10.80(10.1.10.80:3306)

  22. Thu Feb 18 18:23:50 2016 - [info]   10.1.10.91(10.1.10.91:3306)

  23. Thu Feb 18 18:23:50 2016 - [info] Alive Slaves:

  24. Thu Feb 18 18:23:50 2016 - [info]   10.1.10.80(10.1.10.80:3306)  Version=5.6.29-log (oldest major version between slaves) log-bin:enabled

  25. Thu Feb 18 18:23:50 2016 - [info]     Replicating from 10.1.10.244(10.1.10.244:3306)

  26. Thu Feb 18 18:23:50 2016 - [info]   10.1.10.91(10.1.10.91:3306)  Version=5.6.29-log (oldest major version between slaves) log-bin:enabled

  27. Thu Feb 18 18:23:50 2016 - [info]     Replicating from 10.1.10.244(10.1.10.244:3306)

  28. Thu Feb 18 18:23:50 2016 - [info] Checking slave configurations..

  29. Thu Feb 18 18:23:50 2016 - [info]  read_only=1 is not set on slave 10.1.10.80(10.1.10.80:3306).

  30. Thu Feb 18 18:23:50 2016 - [warning]  relay_log_purge=0 is not set on slave 10.1.10.80(10.1.10.80:3306).

  31. Thu Feb 18 18:23:50 2016 - [info]  read_only=1 is not set on slave 10.1.10.91(10.1.10.91:3306).

  32. Thu Feb 18 18:23:50 2016 - [warning]  relay_log_purge=0 is not set on slave 10.1.10.91(10.1.10.91:3306).

  33. Thu Feb 18 18:23:50 2016 - [info] Checking replication filtering settings..

  34. Thu Feb 18 18:23:50 2016 - [info]  Replication filtering check ok.

  35. Thu Feb 18 18:23:50 2016 - [info] Master is down!

  36. Thu Feb 18 18:23:50 2016 - [info] Terminating monitoring script.

  37. Thu Feb 18 18:23:50 2016 - [info] Got exit code 20 (Master dead).

  38. Thu Feb 18 18:23:50 2016 - [info] MHA::MasterFailover version 0.56.

  39. Thu Feb 18 18:23:50 2016 - [info] Starting master failover.

  40. Thu Feb 18 18:23:50 2016 - [info]

  41. Thu Feb 18 18:23:50 2016 - [info] * Phase 1: Configuration Check Phase..

  42. Thu Feb 18 18:23:50 2016 - [info]

  43. Thu Feb 18 18:23:51 2016 - [info] GTID failover mode = 0

  44. Thu Feb 18 18:23:51 2016 - [info] Dead Servers:

  45. Thu Feb 18 18:23:51 2016 - [info]   10.1.10.244(10.1.10.244:3306)

  46. Thu Feb 18 18:23:51 2016 - [info] Checking master reachability via MySQL(double check)...

  47. Thu Feb 18 18:23:52 2016 - [info]  ok.

  48. Thu Feb 18 18:23:52 2016 - [info] Alive Servers:

  49. Thu Feb 18 18:23:52 2016 - [info]   10.1.10.80(10.1.10.80:3306)

  50. Thu Feb 18 18:23:52 2016 - [info]   10.1.10.91(10.1.10.91:3306)

  51. Thu Feb 18 18:23:52 2016 - [info] Alive Slaves:

  52. Thu Feb 18 18:23:52 2016 - [info]   10.1.10.80(10.1.10.80:3306)  Version=5.6.29-log (oldest major version between slaves) log-bin:enabled

  53. Thu Feb 18 18:23:52 2016 - [info]     Replicating from 10.1.10.244(10.1.10.244:3306)

  54. Thu Feb 18 18:23:52 2016 - [info]   10.1.10.91(10.1.10.91:3306)  Version=5.6.29-log (oldest major version between slaves) log-bin:enabled

  55. Thu Feb 18 18:23:52 2016 - [info]     Replicating from 10.1.10.244(10.1.10.244:3306)

  56. Thu Feb 18 18:23:52 2016 - [info] Starting Non-GTID based failover.

  57. Thu Feb 18 18:23:52 2016 - [info]

  58. Thu Feb 18 18:23:52 2016 - [info] ** Phase 1: Configuration Check Phase completed.

  59. Thu Feb 18 18:23:52 2016 - [info]

  60. Thu Feb 18 18:23:52 2016 - [info] * Phase 2: Dead Master Shutdown Phase..

  61. Thu Feb 18 18:23:52 2016 - [info]

  62. Thu Feb 18 18:23:52 2016 - [info] Forcing shutdown so that applications never connect to the current master..

  63. Thu Feb 18 18:23:52 2016 - [warning] master_ip_failover_script is not set. Skipping invalidating dead master IP address.

  64. Thu Feb 18 18:23:52 2016 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.

  65. Thu Feb 18 18:23:53 2016 - [info] * Phase 2: Dead Master Shutdown Phase completed.

  66. Thu Feb 18 18:23:53 2016 - [info]

  67. Thu Feb 18 18:23:53 2016 - [info] * Phase 3: Master Recovery Phase..

  68. Thu Feb 18 18:23:53 2016 - [info]

  69. Thu Feb 18 18:23:53 2016 - [info] * Phase 3.1: Getting Latest Slaves Phase..

  70. Thu Feb 18 18:23:53 2016 - [info]

  71. Thu Feb 18 18:23:53 2016 - [info] The latest binary log file/position on all slaves is data01-bin.000016:120

  72. Thu Feb 18 18:23:53 2016 - [info] Latest slaves (Slaves that received relay log files to the latest):

  73. Thu Feb 18 18:23:53 2016 - [info]   10.1.10.80(10.1.10.80:3306)  Version=5.6.29-log (oldest major version between slaves) log-bin:enabled

  74. Thu Feb 18 18:23:53 2016 - [info]     Replicating from 10.1.10.244(10.1.10.244:3306)

  75. Thu Feb 18 18:23:53 2016 - [info]   10.1.10.91(10.1.10.91:3306)  Version=5.6.29-log (oldest major version between slaves) log-bin:enabled

  76. Thu Feb 18 18:23:53 2016 - [info]     Replicating from 10.1.10.244(10.1.10.244:3306)

  77. Thu Feb 18 18:23:53 2016 - [info] The oldest binary log file/position on all slaves is data01-bin.000016:120

  78. Thu Feb 18 18:23:53 2016 - [info] Oldest slaves:

  79. Thu Feb 18 18:23:53 2016 - [info]   10.1.10.80(10.1.10.80:3306)  Version=5.6.29-log (oldest major version between slaves) log-bin:enabled

  80. Thu Feb 18 18:23:53 2016 - [info]     Replicating from 10.1.10.244(10.1.10.244:3306)

  81. Thu Feb 18 18:23:53 2016 - [info]   10.1.10.91(10.1.10.91:3306)  Version=5.6.29-log (oldest major version between slaves) log-bin:enabled

  82. Thu Feb 18 18:23:53 2016 - [info]     Replicating from 10.1.10.244(10.1.10.244:3306)

  83. Thu Feb 18 18:23:53 2016 - [info]

  84. Thu Feb 18 18:23:53 2016 - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..

  85. Thu Feb 18 18:23:53 2016 - [info]

  86. Thu Feb 18 18:23:53 2016 - [warning] Dead Master is not SSH reachable. Could not save it's binlogs. Transactions that were not sent to the latest slave (Read_Master_Log_Pos to the tail of the dead master's binlog) were lost.

  87. Thu Feb 18 18:23:53 2016 - [info]

  88. Thu Feb 18 18:23:53 2016 - [info] * Phase 3.3: Determining New Master Phase..

  89. Thu Feb 18 18:23:53 2016 - [info]

  90. Thu Feb 18 18:23:53 2016 - [info] Finding the latest slave that has all relay logs for recovering other slaves..

  91. Thu Feb 18 18:23:53 2016 - [info] All slaves received relay logs to the same position. No need to resync each other.

  92. Thu Feb 18 18:23:53 2016 - [info] Searching new master from slaves..

  93. Thu Feb 18 18:23:53 2016 - [info]  Candidate masters from the configuration file:

  94. Thu Feb 18 18:23:53 2016 - [info]  Non-candidate masters:

  95. Thu Feb 18 18:23:53 2016 - [info] New master is 10.1.10.80(10.1.10.80:3306)

  96. Thu Feb 18 18:23:53 2016 - [info] Starting master failover..

  97. Thu Feb 18 18:23:53 2016 - [info]

  98. From:

  99. 10.1.10.244(10.1.10.244:3306) (current master)

  100. +--10.1.10.80(10.1.10.80:3306)

  101. +--10.1.10.91(10.1.10.91:3306)


  103. To:

  104. 10.1.10.80(10.1.10.80:3306) (new master)

  105. +--10.1.10.91(10.1.10.91:3306)

  106. Thu Feb 18 18:23:53 2016 - [info]

  107. Thu Feb 18 18:23:53 2016 - [info] * Phase 3.3: New Master Diff Log Generation Phase..

  108. Thu Feb 18 18:23:53 2016 - [info]

  109. Thu Feb 18 18:23:53 2016 - [info]  This server has all relay logs. No need to generate diff files from the latest slave.

  110. Thu Feb 18 18:23:53 2016 - [info]

  111. Thu Feb 18 18:23:53 2016 - [info] * Phase 3.4: Master Log Apply Phase..

  112. Thu Feb 18 18:23:53 2016 - [info]

  113. Thu Feb 18 18:23:53 2016 - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.

  114. Thu Feb 18 18:23:53 2016 - [info] Starting recovery on 10.1.10.80(10.1.10.80:3306)..

  115. Thu Feb 18 18:23:53 2016 - [info]  This server has all relay logs. Waiting all logs to be applied..

  116. Thu Feb 18 18:23:53 2016 - [info]   done.

  117. Thu Feb 18 18:23:53 2016 - [info]  All relay logs were successfully applied.

  118. Thu Feb 18 18:23:53 2016 - [info] Getting new master's binlog name and position..

  119. Thu Feb 18 18:23:53 2016 - [info]  data02-bin.000003:684

  120. Thu Feb 18 18:23:53 2016 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='10.1.10.80', MASTER_PORT=3306, MASTER_LOG_FILE='data02-bin.000003', MASTER_LOG_POS=684, MASTER_USER='repl_user', MASTER_PASSWORD='xxx';

  121. Thu Feb 18 18:23:53 2016 - [warning] master_ip_failover_script is not set. Skipping taking over new master IP address.

  122. Thu Feb 18 18:23:53 2016 - [info] ** Finished master recovery successfully.

  123. Thu Feb 18 18:23:53 2016 - [info] * Phase 3: Master Recovery Phase completed.

  124. Thu Feb 18 18:23:53 2016 - [info]

  125. Thu Feb 18 18:23:53 2016 - [info] * Phase 4: Slaves Recovery Phase..

  126. Thu Feb 18 18:23:53 2016 - [info]

  127. Thu Feb 18 18:23:53 2016 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..

  128. Thu Feb 18 18:23:53 2016 - [info]

  129. Thu Feb 18 18:23:53 2016 - [info] -- Slave diff file generation on host 10.1.10.91(10.1.10.91:3306) started, pid: 18577. Check tmp log /var/log/mha//10.1.10.91_3306_20160218182350.log if it takes time..

  130. Thu Feb 18 18:23:54 2016 - [info]

  131. Thu Feb 18 18:23:54 2016 - [info] Log messages from 10.1.10.91 ...

  132. Thu Feb 18 18:23:54 2016 - [info]

  133. Thu Feb 18 18:23:53 2016 - [info]  This server has all relay logs. No need to generate diff files from the latest slave.

  134. Thu Feb 18 18:23:54 2016 - [info] End of log messages from 10.1.10.91.

  135. Thu Feb 18 18:23:54 2016 - [info] -- 10.1.10.91(10.1.10.91:3306) has the latest relay log events.

  136. Thu Feb 18 18:23:54 2016 - [info] Generating relay diff files from the latest slave succeeded.

  137. Thu Feb 18 18:23:54 2016 - [info]

  138. Thu Feb 18 18:23:54 2016 - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..

  139. Thu Feb 18 18:23:54 2016 - [info]

  140. Thu Feb 18 18:23:54 2016 - [info] -- Slave recovery on host 10.1.10.91(10.1.10.91:3306) started, pid: 18579. Check tmp log /var/log/mha//10.1.10.91_3306_20160218182350.log if it takes time..

  141. Thu Feb 18 18:23:55 2016 - [info]

  142. Thu Feb 18 18:23:55 2016 - [info] Log messages from 10.1.10.91 ...

  143. Thu Feb 18 18:23:55 2016 - [info]

  144. Thu Feb 18 18:23:54 2016 - [info] Starting recovery on 10.1.10.91(10.1.10.91:3306)..

  145. Thu Feb 18 18:23:54 2016 - [info]  This server has all relay logs. Waiting all logs to be applied..

  146. Thu Feb 18 18:23:54 2016 - [info]   done.

  147. Thu Feb 18 18:23:54 2016 - [info]  All relay logs were successfully applied.

  148. Thu Feb 18 18:23:54 2016 - [info]  Resetting slave 10.1.10.91(10.1.10.91:3306) and starting replication from the new master 10.1.10.80(10.1.10.80:3306)..

  149. Thu Feb 18 18:23:54 2016 - [info]  Executed CHANGE MASTER.

  150. Thu Feb 18 18:23:54 2016 - [info]  Slave started.

  151. Thu Feb 18 18:23:55 2016 - [info] End of log messages from 10.1.10.91.

  152. Thu Feb 18 18:23:55 2016 - [info] -- Slave recovery on host 10.1.10.91(10.1.10.91:3306) succeeded.

  153. Thu Feb 18 18:23:55 2016 - [info] All new slave servers recovered successfully.

  154. Thu Feb 18 18:23:55 2016 - [info]

  155. Thu Feb 18 18:23:55 2016 - [info] * Phase 5: New master cleanup phase..

  156. Thu Feb 18 18:23:55 2016 - [info]

  157. Thu Feb 18 18:23:55 2016 - [info] Resetting slave info on the new master..

  158. Thu Feb 18 18:23:55 2016 - [info]  10.1.10.80: Resetting slave info succeeded.

  159. Thu Feb 18 18:23:55 2016 - [info] Master failover to 10.1.10.80(10.1.10.80:3306) completed successfully.

  160. Thu Feb 18 18:23:55 2016 - [info]


  162. ----- Failover Report -----


  164. mha-manager: MySQL Master failover 10.1.10.244(10.1.10.244:3306) to 10.1.10.80(10.1.10.80:3306) succeeded


  166. Master 10.1.10.244(10.1.10.244:3306) is down!


  168. Check MHA Manager logs at manager:/var/log/mha/manager.log for details.


  170. Started automated(non-interactive) failover.

  171. The latest slave 10.1.10.80(10.1.10.80:3306) has all relay logs for recovery.

  172. Selected 10.1.10.80(10.1.10.80:3306) as a new master.

  173. 10.1.10.80(10.1.10.80:3306): OK: Applying all logs succeeded.

  174. 10.1.10.91(10.1.10.91:3306): This host has the latest relay log events.

  175. Generating relay diff files from the latest slave succeeded.

  176. 10.1.10.91(10.1.10.91:3306): OK: Applying all logs succeeded. Slave started, replicating from 10.1.10.80(10.1.10.80:3306)

  177. 10.1.10.80(10.1.10.80:3306): Resetting slave info succeeded.

  178. Master failover to 10.1.10.80(10.1.10.80:3306) completed successfully.




模擬結(jié)束

測(cè)的不太多，目前知道的一個(gè)坑：
mha建議關(guān)閉relay_log_purge，以保證用于有足夠的中繼日志去恢復(fù)其他的從庫(kù)，也就是需要將relay_log_purge=0，導(dǎo)致relay-log無法定期清理。
可能需要手動(dòng)添加定時(shí)任務(wù)來清理，清理方式可以是：
 ....../purge_relay_logs --user=$user --password=$password–disable_relay_log_purge >> ....../log/purge_relay_logs.log 2>&1



當(dāng)然還需要配合vip節(jié)點(diǎn)等保證應(yīng)用透明性，實(shí)現(xiàn)failover。

以上是“MySQL中HA MHA如何搭建”這篇文章的所有內(nèi)容，感謝各位的閱讀！相信大家都有了一定的了解，希望分享的內(nèi)容對(duì)大家有所幫助，如果還想學(xué)習(xí)更多知識(shí)，歡迎關(guān)注億速云行業(yè)資訊頻道！

向AI問一下細(xì)節(jié)

免責(zé)聲明：本站發(fā)布的內(nèi)容（圖片、視頻和文字）以原創(chuàng)、轉(zhuǎn)載和分享為主，文章觀點(diǎn)不代表本網(wǎng)站立場(chǎng)，如果涉及侵權(quán)請(qǐng)聯(lián)系站長(zhǎng)郵箱：is@yisu.com進(jìn)行舉報(bào)，并提供相關(guān)證據(jù)，一經(jīng)查實(shí)，將立刻刪除涉嫌侵權(quán)內(nèi)容。

AI
助
手