AI 助理
备案控制台
开发者社区 数据库 文章 正文

Mysql5.5部署MHA

2017-11-28 1258
版权
版权声明：
本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《 阿里云开发者社区用户服务协议》和 《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写 侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
本文涉及的产品
RDS MySQL Serverless 基础系列，0.5-2RCU 50GB
推荐场景：
学生管理系统数据库设计 搭建个人博客
云数据库 RDS MySQL，集群系列 2核4GB
推荐场景：
搭建个人博客
RDS MySQL Serverless 高可用系列，价值2615元额度，1个月
简介：

MHA分管理节点和数据库节点，数据库节点由mysql主从或者主主从构成，当主库挂掉后，管理节点会自动将从节点提升为主节点；管理节点的角色类似于oracle数据库中的fast start failover中的observer，但mha上层可以通过keepalive部署VIP，程序连接数据库使用VIP，从而实现后台数据库的故障切换透明化

MHA节点包含三个脚本，依赖perl模块；
save_binary_logs:保存和复制当掉的主服务器二进制日志；
apply_diff_relay_logs:识别差异的relay log事件，并应用于其他salve服务器；
purge_relay_logs:清除relay log文件；
需要在所有mysql服务器上安装MHA节点，MHA管理服务器也需要安装。MHA管理节点模块内部依赖MHA节点模块；
MHA管理节点通过ssh连接管理mysql服务器和执行MHA节点脚本。MHA节点依赖perl的DBD::mysql模块;

本文环境介绍，操作系统均为rhel5.4
主库：192.168.123.13/dg53.yang.com
备库：192.168.123.14/dg54.yang.com
管理节点：192.168.123.15/dg55.yang.com

在开始之前，请先配置好服务器间的时间同步和名称解析

一:在数据库节点安装mha node

 

     
 
  1. [root@dg53 ~]# rpm -ivh http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm  
    2.  
 
  2. Retrieving http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm  
    3.  
 
  3. warning: /var/tmp/rpm-xfer.yqwfYT: Header V3 DSA signature: NOKEY, key ID 217521f6  
    4.  
 
  4. Preparing...                ########################################### [100%]  
    5.  
 
  5.    1:epel-release           ########################################### [100%]  
    6.  
 
  6.  
    7.  
 
  7. [root@dg53 ~]# ls /etc/yum.repos.d/  
    8.  
 
  8. base.repo  epel.repo  epel-testing.repo  rhel-debuginfo.repo  
    9.  
 
  9. [root@dg53 ~]# yum -y install perl-DBD-MySQL  ncftp  
    10.  
 
  10. [root@dg53 ~]#  wget http://mysql-master-ha.googlecode.com/files/mha4mysql-node-0.52.tar.gz -P /usr/local/src/tarbag/  
    11.  
 
  11. [root@dg53 ~]# cd /usr/local/src/tarbag/  
    12.  
 
  12. [root@dg53 tarbag]# tar -zxvpf mha4mysql-node-0.52.tar.gz -C ../software/  
    13.  
 
  13. [root@dg53 tarbag]# cd ../software/mha4mysql-node-0.52/  
    14.  
 
  14. [root@dg53 mha4mysql-node-0.52]# perl Makefile.PL   
    15.  
 
  15. [root@dg53 mha4mysql-node-0.52]# make && make install 
    16.  

 

二：管理节点
 1：按照步骤一安装mha node
 

2:安装mha manager
 

 

     
 
  1. [root@dg55 ~]# yum -y install perl-Config-Tiny perl-Params-Validate perl-Log-Dispatch perl-Parallel-ForkManager  
    2.  
 
  2. [root@dg55 ~]# wget http://mysql-master-ha.googlecode.com/files/mha4mysql-manager-0.52.tar.gz -P /usr/local/src/tarbag/  
    3.  
 
  3. [root@dg55 ~]# cd /usr/local/src/tarbag/  
    4.  
 
  4. [root@dg55 tarbag]# tar -zxvpf mha4mysql-manager-0.52.tar.gz -C ../software/  
    5.  
 
  5. [root@dg55 tarbag]# cd ../software/mha4mysql-manager-0.52/  
    6.  
 
  6. [root@dg55 mha4mysql-manager-0.52]# perl Makefile.PL  
    7.  
 
  7. [root@dg55 mha4mysql-manager-0.52]# make && make install 
    8.  

 

3:编辑配置文件
 

 

     
 
  1. [root@dg55 mha4mysql-manager-0.52]# mkdir /etc/masterha  
    2.  
 
  2. [root@dg55 mha4mysql-manager-0.52]# mkdir -p /masterha/app1  
    3.  
 
  3. [root@dg55 mha4mysql-manager-0.52]# cp samples/conf/* /etc/masterha/  
    4.  
 
  4. [root@dg55 mha4mysql-manager-0.52]# cat /etc/masterha/app1.cnf   
    5.  
 
  5. [server default]  
    6.  
 
  6.  manager_workdir=/masterha/app1   
    7.  
 
  7.  manager_log=/masterha/app1/manager.log   
    8.  
 
  8.  user=root  
    9.  
 
  9.  password=123456  
    10.  
 
  10.  ssh_user=root  
    11.  
 
  11.  repl_user=r_test  
    12.  
 
  12.  repl_password=123456  
    13.  
 
  13.  ping_interval=1  
    14.  
 
  14.  shutdown_script=""  
    15.  
 
  15.  #master_ip_failover_script="/usr/local/bin/master_ip_failover"  
    16.  
 
  16.  master_ip_online_change_script=""  
    17.  
 
  17.  report_script=""  
    18.  
 
  18. [server1]  
    19.  
 
  19.  hostname=192.168.123.13   
    20.  
 
  20.  master_binlog_dir="/mydata"  
    21.  
 
  21.  candidate_master=1  
    22.  
 
  22. [server2]  
    23.  
 
  23.  hostname=192.168.123.14   
    24.  
 
  24.  master_binlog_dir="/mydata"  
    25.  
 
  25.  candidate_master=1  
    26.  

 

4:配置manager节点和node节点以及node节点间的ssh公钥信任
 

 

     
 
  1. [root@dg55 ~]# ssh-keygen -t rsa  
    2.  
 
  2. [root@dg55 ~]# ssh-copy-id -i /root/.ssh/id_rsa.pub root@192.168.123.13  
    3.  
 
  3. [root@dg55 ~]# ssh-copy-id -i /root/.ssh/id_rsa.pub root@192.168.123.14  
    4.  
 
  4.  
    5.  
 
  5. [root@dg55 ~]# ssh 192.168.123.13 "ifconfig |grep 'inet addr' |head -1"  
    6.  
 
  6.           inet addr:192.168.123.13  Bcast:192.168.123.255  Mask:255.255.255.0  
    7.  
 
  7. [root@dg55 ~]# ssh 192.168.123.14 "ifconfig |grep 'inet addr' |head -1"  
    8.  
 
  8.           inet addr:192.168.123.14  Bcast:192.168.123.255  Mask:255.255.255.0 
    9.  

 

5：测试ssh连接
 

 

     
 
  1. [root@dg55 ~]# masterha_check_ssh --conf=/etc/masterha/app1.cnf   
    2.  
 
  2. Wed Jun  6 11:11:25 2012 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.  
    3.  
 
  3. Wed Jun  6 11:11:25 2012 - [info] Reading application default configurations from /etc/masterha/app1.cnf..  
    4.  
 
  4. Wed Jun  6 11:11:25 2012 - [info] Reading server configurations from /etc/masterha/app1.cnf..  
    5.  
 
  5. Wed Jun  6 11:11:25 2012 - [info] Starting SSH connection tests..  
    6.  
 
  6. Wed Jun  6 11:11:25 2012 - [debug]   
    7.  
 
  7. Wed Jun  6 11:11:25 2012 - [debug]  Connecting via SSH from root@192.168.123.13(192.168.123.13) to root@192.168.123.14(192.168.123.14)..  
    8.  
 
  8. Wed Jun  6 11:11:25 2012 - [debug]   ok.  
    9.  
 
  9. Wed Jun  6 11:11:26 2012 - [debug]   
    10.  
 
  10. Wed Jun  6 11:11:25 2012 - [debug]  Connecting via SSH from root@192.168.123.14(192.168.123.14) to root@192.168.123.13(192.168.123.13)..  
    11.  
 
  11. Wed Jun  6 11:11:26 2012 - [debug]   ok.  
    12.  
 
  12. Wed Jun  6 11:11:26 2012 - [info] All SSH connection tests passed successfully. 
    13.  

 

6：测试主从复制情况，默认使用root用户连接
 

 

     
 
  1. mysql> select user,host,password from mysql.user;  
    2.  
 
  2. +--------+----------------+-------------------------------------------+  
    3.  
 
  3. | user   | host           | password                                  |  
    4.  
 
  4. +--------+----------------+-------------------------------------------+  
    5.  
 
  5. | root   | localhost      |                                           |   
    6.  
 
  6. | root   | dg53.yang.com  |                                           |   
    7.  
 
  7. | root   | 127.0.0.1      |                                           |   
    8.  
 
  8. | root   | ::1            |                                           |   
    9.  
 
  9. |        | localhost      |                                           |   
    10.  
 
  10. |        | dg53.yang.com  |                                           |   
    11.  
 
  11. | r_test | 192.168.123.14 | *6BB4837EB74329105EE4568DDA7DC67ED2CA2AD9 |   
    12.  
 
  12. +--------+----------------+-------------------------------------------+  
    13.  
 
  13. 7 rows in set (0.08 sec)  
    14.  
 
  14.  
    15.  
 
  15.  mysql> use mysql;   
    16.  
 
  16. Database changed  
    17.  
 
  17.  
    18.  
 
  18.  mysql> update user set host='192.168.123.%' where user='r_test';   
    19.  
 
  19. Query OK, 1 row affected (0.05 sec)  
    20.  
 
  20. Rows matched: 1  Changed: 1  Warnings: 0  
    21.  
 
  21.  
    22.  
 
  22.  mysql> commit;   
    23.  
 
  23. Query OK, 0 rows affected (0.01 sec)  
    24.  
 
  24.  
    25.  
 
  25.  mysql> update user set host='192.168.123.%' where host='localhost' and user='root' and password='';   
    26.  
 
  26. Query OK, 0 rows affected (0.00 sec)  
    27.  
 
  27. Rows matched: 1  Changed: 1  Warnings: 0  
    28.  
 
  28.  
    29.  
 
  29.  mysql> update user set password=PASSWORD('123456') where user='root' and host='192.168.123.%';   
    30.  
 
  30. Query OK, 0 rows affected (0.00 sec)  
    31.  
 
  31. Rows matched: 1  Changed: 0  Warnings: 0  
    32.  
 
  32.  
    33.  
 
  33.  mysql> flush privileges;   
    34.  
 
  34. Query OK, 0 rows affected (0.02 sec)  
    35.  
 
  35.  
    36.  
 
  36. [root@dg53 ~]# whereis mysqlbinlog  
    37.  
 
  37. mysqlbinlog: /usr/bin/mysqlbinlog  
    38.  
 
  38.  
    39.  
 
  39. [root@dg53 ~]# mv /usr/bin/mysql* /tmp  
    40.  
 
  40. [root@dg54 ~]# mv /usr/bin/mysql* /tmp  
    41.  
 
  41. [root@dg53 ~]# ln -s /usr/local/mysql5.5.25/bin/* /usr/local/bin/  
    42.  
 
  42. [root@dg54 ~]# ln -s /usr/local/mysql5.5.25/bin/* /usr/local/bin/  
    43.  
 
  43.  
    44.  
 
  44.  [root@dg55 ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf    
    45.  
 
  45. Wed Jun  6 12:39:03 2012 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.  
    46.  
 
  46. Wed Jun  6 12:39:03 2012 - [info] Reading application default configurations from /etc/masterha/app1.cnf..  
    47.  
 
  47. Wed Jun  6 12:39:03 2012 - [info] Reading server configurations from /etc/masterha/app1.cnf..  
    48.  
 
  48. Wed Jun  6 12:39:03 2012 - [info] MHA::MasterMonitor version 0.52.  
    49.  
 
  49. Wed Jun  6 12:39:03 2012 - [info] Dead Servers:  
    50.  
 
  50. Wed Jun  6 12:39:03 2012 - [info] Alive Servers:  
    51.  
 
  51. Wed Jun  6 12:39:03 2012 - [info]   192.168.123.13(192.168.123.13:3306)  
    52.  
 
  52. Wed Jun  6 12:39:03 2012 - [info]   192.168.123.14(192.168.123.14:3306)  
    53.  
 
  53. Wed Jun  6 12:39:03 2012 - [info] Alive Slaves:  
    54.  
 
  54.  Wed Jun  6 12:39:03 2012 - [info]   192.168.123.14(192.168.123.14:3306)  Version=5.5.25-log (oldest major version between slaves) log-bin:enabled   
    55.  
 
  55. Wed Jun  6 12:39:03 2012 - [info]     Replicating from 192.168.123.13(192.168.123.13:3306)  
    56.  
 
  56. Wed Jun  6 12:39:03 2012 - [info]     Primary candidate for the new Master (candidate_master is set)  
    57.  
 
  57. Wed Jun  6 12:39:03 2012 - [info] Current Alive Master: 192.168.123.13(192.168.123.13:3306)  
    58.  
 
  58. Wed Jun  6 12:39:03 2012 - [info] Checking slave configurations..  
    59.  
 
  59.  Wed Jun  6 12:39:03 2012 - [warning]  read_only=1 is not set on slave 192.168.123.14(192.168.123.14:3306).   
    60.  
 
  60.  Wed Jun  6 12:39:03 2012 - [warning]  relay_log_purge=0 is not set on slave 192.168.123.14(192.168.123.14:3306).   
    61.  
 
  61. Wed Jun  6 12:39:03 2012 - [info] Checking replication filtering settings..  
    62.  
 
  62.  Wed Jun  6 12:39:03 2012 - [info]  binlog_do_db= bbs,test, binlog_ignore_db= mysql  
    63.  
 
  63. Wed Jun  6 12:39:03 2012 - [info]  Replication filtering check ok.  
    64.  
 
  64. Wed Jun  6 12:39:03 2012 - [info] Starting SSH connection tests..  
    65.  
 
  65. Wed Jun  6 12:39:05 2012 - [info] All SSH connection tests passed successfully.  
    66.  
 
  66. Wed Jun  6 12:39:05 2012 - [info] Checking MHA Node version..  
    67.  
 
  67. Wed Jun  6 12:39:05 2012 - [info]  Version check ok.  
    68.  
 
  68. Wed Jun  6 12:39:05 2012 - [info] Checking SSH publickey authentication and checking recovery script configurations on the current master..  
    69.  
 
  69.  Wed Jun  6 12:39:05 2012 - [info]   Executing command: save_binary_logs --command=test --start_file=mysql-bin.000011 --start_pos=4 --binlog_dir=/mydata --output_file=/var/tmp/save_binary_logs_test --manager_version=0.52    
    70.  
 
  70. Wed Jun  6 12:39:05 2012 - [info]   Connecting to root@192.168.123.13(192.168.123.13)..   
    71.  
 
  71.   Creating /var/tmp if not exists..    ok.  
    72.  
 
  72.   Checking output directory is accessible or not..  
    73.  
 
  73.    ok.  
    74.  
 
  74.   Binlog found at /mydata, up to mysql-bin.000011  
    75.  
 
  75. Wed Jun  6 12:39:06 2012 - [info] Master setting check done.  
    76.  
 
  76. Wed Jun  6 12:39:06 2012 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..  
    77.  
 
  77.  Wed Jun  6 12:39:06 2012 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user=root --slave_host=192.168.123.14 --slave_ip=192.168.123.14 --slave_port=3306 --workdir=/var/tmp --target_version=5.5.25-log --manager_version=0.52 --relay_log_info=/mydata/relay-log.info  --slave_pass=xxx  
    78.  
 
  78. Wed Jun  6 12:39:06 2012 - [info]   Connecting to root@192.168.123.14(192.168.123.14)..   
    79.  
 
  79.   Checking slave recovery environment settings..  
    80.  
 
  80.     Opening /mydata/relay-log.info ... ok.  
    81.  
 
  81.     Relay log found at /mydata, up to dg54-relay-bin.000019  
    82.  
 
  82.     Temporary relay log file is /mydata/dg54-relay-bin.000019  
    83.  
 
  83.     Testing mysql connection and privileges.. done.  
    84.  
 
  84.     Testing mysqlbinlog output.. done.  
    85.  
 
  85.     Cleaning up test file(s).. done.  
    86.  
 
  86. Wed Jun  6 12:39:06 2012 - [info] Slaves settings check done.  
    87.  
 
  87. Wed Jun  6 12:39:06 2012 - [info]   
    88.  
 
  88. 192.168.123.13 (current master)  
    89.  
 
  89.  +--192.168.123.14  
    90.  
 
  90.  
    91.  
 
  91. Wed Jun  6 12:39:06 2012 - [info] Checking replication health on 192.168.123.14..  
    92.  
 
  92. Wed Jun  6 12:39:06 2012 - [info]  ok.  
    93.  
 
  93. Wed Jun  6 12:39:06 2012 - [warning] master_ip_failover_script is not defined.  
    94.  
 
  94. Wed Jun  6 12:39:06 2012 - [warning] shutdown_script is not defined.  
    95.  
 
  95. Wed Jun  6 12:39:06 2012 - [info] Got exit code 0 (Not master dead).  
    96.  
 
  96.  
    97.  
 
  97. MySQL Replication Health is OK. 
    98.  

 

7：启动管理节点进程
 

 

     
 
  1. [root@dg55 ~]# nohup masterha_manager --conf=/etc/masterha/app1.cnf > /tmp/mha_manager.log  < /dev/null 2>&1 &  
    2.  
 
  2. [1] 25516  
    3.  
 
  3.  [root@dg55 ~]# masterha_check_status --conf=/etc/masterha/app1.cnf    
    4.  
 
  4. app1 (pid:25516) is running(0:PING_OK), master:192.168.123.13 
    5.  

 

三：测试failover过程
 1：当前主库为192.168.123.13，关闭主库
 

 

     
 
  1. mysql> show slave hosts;  
    2.  
 
  2. +-----------+------+------+-----------+  
    3.  
 
  3. | Server_id | Host | Port | Master_id |  
    4.  
 
  4. +-----------+------+------+-----------+  
    5.  
 
  5. |         2 |      | 3306 |         1 |  
    6.  
 
  6. +-----------+------+------+-----------+  
    7.  
 
  7. 1 row in set (0.00 sec)  
    8.  
 
  8.  
    9.  
 
  9. [root@dg53 ~]# service mysqld stop  
    10.  
 
  10. Shutting down MySQL...[  OK  ] 
    11.  

 

2：在管理节点上观察日志输出
 

 


 
  

    
[root@dg55 ~]# tail -f /masterha/app1/manager.log 
 Wed Jun  6 14:50:48 2012 - [info] 
 192.168.123.13 (current master)
  +--192.168.123.14
 
Wed Jun  6 14:50:48 2012 - [warning] master_ip_failover_script is not defined.
 Wed Jun  6 14:50:48 2012 - [warning] shutdown_script is not defined.
 Wed Jun  6 14:50:48 2012 - [info] Set master ping interval 1 seconds.
 Wed Jun  6 14:50:48 2012 - [warning] secondary_check_script is not defined. It is highly recommended setting it to check master reachability from two or more routes.
 Wed Jun  6 14:50:48 2012 - [info] Starting ping health check on 192.168.123.13(192.168.123.13:3306)..
 Wed Jun  6 14:50:48 2012 - [info] Ping succeeded, sleeping until it doesn't respond..
 
Wed Jun  6 14:51:32 2012 - [warning] Got error on MySQL ping: 2006 (MySQL server has gone away)
 Wed Jun  6 14:51:32 2012 - [info] HealthCheck: SSH to 192.168.123.13 is reachable.
 Wed Jun  6 14:51:33 2012 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)
 Wed Jun  6 14:51:33 2012 - [warning] Connection failed 1 time(s)..
 Wed Jun  6 14:51:34 2012 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)
 Wed Jun  6 14:51:34 2012 - [warning] Connection failed 2 time(s)..
 Wed Jun  6 14:51:35 2012 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)
 Wed Jun  6 14:51:35 2012 - [warning] Connection failed 3 time(s)..
 Wed Jun  6 14:51:35 2012 - [warning] Master is not reachable from health checker!
 Wed Jun  6 14:51:35 2012 - [warning] Master 192.168.123.13(192.168.123.13:3306) is not reachable!
 Wed Jun  6 14:51:35 2012 - [warning] SSH is reachable.
 Wed Jun  6 14:51:35 2012 - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/masterha/app1.cnf again, and trying to connect to all servers to check server status..
 Wed Jun  6 14:51:35 2012 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
 Wed Jun  6 14:51:35 2012 - [info] Reading application default configurations from /etc/masterha/app1.cnf..
 Wed Jun  6 14:51:35 2012 - [info] Reading server configurations from /etc/masterha/app1.cnf..
 Wed Jun  6 14:51:35 2012 - [info] Dead Servers:
 Wed Jun  6 14:51:35 2012 - [info]   192.168.123.13(192.168.123.13:3306)
 Wed Jun  6 14:51:35 2012 - [info] Alive Servers:
 Wed Jun  6 14:51:35 2012 - [info]   192.168.123.14(192.168.123.14:3306)
 Wed Jun  6 14:51:35 2012 - [info] Alive Slaves:
 Wed Jun  6 14:51:35 2012 - [info]   192.168.123.14(192.168.123.14:3306)  Version=5.5.25-log (oldest major version between slaves) log-bin:enabled
 Wed Jun  6 14:51:35 2012 - [info]     Replicating from 192.168.123.13(192.168.123.13:3306)
 Wed Jun  6 14:51:35 2012 - [info]     Primary candidate for the new Master (candidate_master is set)
 Wed Jun  6 14:51:35 2012 - [info] Checking slave configurations..
 Wed Jun  6 14:51:35 2012 - [warning]  read_only=1 is not set on slave 192.168.123.14(192.168.123.14:3306).
 Wed Jun  6 14:51:35 2012 - [warning]  relay_log_purge=0 is not set on slave 192.168.123.14(192.168.123.14:3306).
 Wed Jun  6 14:51:35 2012 - [info] Checking replication filtering settings..
 Wed Jun  6 14:51:35 2012 - [info]  Replication filtering check ok.
 Wed Jun  6 14:51:35 2012 - [info] Master is down!
 Wed Jun  6 14:51:35 2012 - [info] Terminating monitoring script.
 Wed Jun  6 14:51:35 2012 - [info] Got exit code 20 (Master dead).
 Wed Jun  6 14:51:35 2012 - [info] MHA::MasterFailover version 0.52.
 Wed Jun  6 14:51:35 2012 - [info] Starting master failover.
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] * Phase 1: Configuration Check Phase..
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] Dead Servers:
 Wed Jun  6 14:51:35 2012 - [info]   192.168.123.13(192.168.123.13:3306)
 Wed Jun  6 14:51:35 2012 - [info] Checking master reachability via mysql(double check)..
 Wed Jun  6 14:51:35 2012 - [info]  ok.
 Wed Jun  6 14:51:35 2012 - [info] Alive Servers:
 Wed Jun  6 14:51:35 2012 - [info]   192.168.123.14(192.168.123.14:3306)
 Wed Jun  6 14:51:35 2012 - [info] Alive Slaves:
 Wed Jun  6 14:51:35 2012 - [info]   192.168.123.14(192.168.123.14:3306)  Version=5.5.25-log (oldest major version between slaves) log-bin:enabled
 Wed Jun  6 14:51:35 2012 - [info]     Replicating from 192.168.123.13(192.168.123.13:3306)
 Wed Jun  6 14:51:35 2012 - [info]     Primary candidate for the new Master (candidate_master is set)
 Wed Jun  6 14:51:35 2012 - [info] ** Phase 1: Configuration Check Phase completed.
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] * Phase 2: Dead Master Shutdown Phase..
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] Forcing shutdown so that applications never connect to the current master..
 Wed Jun  6 14:51:35 2012 - [warning] master_ip_failover_script is not set. Skipping invalidating dead master ip address.
 Wed Jun  6 14:51:35 2012 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
 Wed Jun  6 14:51:35 2012 - [info] * Phase 2: Dead Master Shutdown Phase completed.
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] * Phase 3: Master Recovery Phase..
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] * Phase 3.1: Getting Latest Slaves Phase..
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] The latest binary log file/position on all slaves is mysql-bin.000021:107
 Wed Jun  6 14:51:35 2012 - [info] Latest slaves (Slaves that received relay log files to the latest):
 Wed Jun  6 14:51:35 2012 - [info]   192.168.123.14(192.168.123.14:3306)  Version=5.5.25-log (oldest major version between slaves) log-bin:enabled
 Wed Jun  6 14:51:35 2012 - [info]     Replicating from 192.168.123.13(192.168.123.13:3306)
 Wed Jun  6 14:51:35 2012 - [info]     Primary candidate for the new Master (candidate_master is set)
 Wed Jun  6 14:51:35 2012 - [info] The oldest binary log file/position on all slaves is mysql-bin.000021:107
 Wed Jun  6 14:51:35 2012 - [info] Oldest slaves:
 Wed Jun  6 14:51:35 2012 - [info]   192.168.123.14(192.168.123.14:3306)  Version=5.5.25-log (oldest major version between slaves) log-bin:enabled
 Wed Jun  6 14:51:35 2012 - [info]     Replicating from 192.168.123.13(192.168.123.13:3306)
 Wed Jun  6 14:51:35 2012 - [info]     Primary candidate for the new Master (candidate_master is set)
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
 Wed Jun  6 14:51:35 2012 - [info] 
 Wed Jun  6 14:51:35 2012 - [info] Fetching dead master's binary logs..
 Wed Jun  6 14:51:35 2012 - [info] Executing command on the dead master 192.168.123.13(192.168.123.13:3306): save_binary_logs --command=save --start_file=mysql-bin.000021  --start_pos=107 --binlog_dir=/mydata --output_file=/var/tmp/saved_master_binlog_from_192.168.123.13_3306_20120606145135.binlog --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.52
   Creating /var/tmp if not exists..    ok.
  Concat binary/relay logs from mysql-bin.000021 pos 107 to mysql-bin.000021 EOF into /var/tmp/saved_master_binlog_from_192.168.123.13_3306_20120606145135.binlog ..
   Dumping binlog format description event, from position 0 to 107.. ok.
   Dumping effective binlog data from /mydata/mysql-bin.000021 position 107 to tail(126).. ok.
  Concat succeeded.
 Wed Jun  6 14:51:36 2012 - [info] scp from root@192.168.123.13:/var/tmp/saved_master_binlog_from_192.168.123.13_3306_20120606145135.binlog to local:/masterha/app1/saved_master_binlog_from_192.168.123.13_3306_20120606145135.binlog succeeded.
 Wed Jun  6 14:51:36 2012 - [info] HealthCheck: SSH to 192.168.123.14 is reachable.
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] * Phase 3.3: Determining New Master Phase..
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] Finding the latest slave that has all relay logs for recovering other slaves..
 Wed Jun  6 14:51:37 2012 - [info] All slaves received relay logs to the same position. No need to resync each other.
 Wed Jun  6 14:51:37 2012 - [info] Searching new master from slaves..
 Wed Jun  6 14:51:37 2012 - [info]  Candidate masters from the configuration file:
 Wed Jun  6 14:51:37 2012 - [info]   192.168.123.14(192.168.123.14:3306)  Version=5.5.25-log (oldest major version between slaves) log-bin:enabled
 Wed Jun  6 14:51:37 2012 - [info]     Replicating from 192.168.123.13(192.168.123.13:3306)
 Wed Jun  6 14:51:37 2012 - [info]     Primary candidate for the new Master (candidate_master is set)
 Wed Jun  6 14:51:37 2012 - [info]  Non-candidate masters:
 Wed Jun  6 14:51:37 2012 - [info]  Searching from candidate_master slaves which have received the latest relay log events..
 Wed Jun  6 14:51:37 2012 - [info] New master is 192.168.123.14(192.168.123.14:3306)
 Wed Jun  6 14:51:37 2012 - [info] Starting master failover..
 Wed Jun  6 14:51:37 2012 - [info] 
 From:
 192.168.123.13 (current master)
  +--192.168.123.14
 
To:
 192.168.123.14 (new master)
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] * Phase 3.3: New Master Diff Log Generation Phase..
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info]  This server has all relay logs. No need to generate diff files from the latest slave.
 Wed Jun  6 14:51:37 2012 - [info] Sending binlog..
 Wed Jun  6 14:51:37 2012 - [info] scp from local:/masterha/app1/saved_master_binlog_from_192.168.123.13_3306_20120606145135.binlog to root@192.168.123.14:/var/tmp/saved_master_binlog_from_192.168.123.13_3306_20120606145135.binlog succeeded.
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] * Phase 3.4: Master Log Apply Phase..
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
 Wed Jun  6 14:51:37 2012 - [info] Starting recovery on 192.168.123.14(192.168.123.14:3306)..
 Wed Jun  6 14:51:37 2012 - [info]  Generating diffs succeeded.
 Wed Jun  6 14:51:37 2012 - [info] Waiting until all relay logs are applied.
 Wed Jun  6 14:51:37 2012 - [info]  done.
 Wed Jun  6 14:51:37 2012 - [info] Getting slave status..
 Wed Jun  6 14:51:37 2012 - [info] This slave(192.168.123.14)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000021:107). No need to recover from Exec_Master_Log_Pos.
 Wed Jun  6 14:51:37 2012 - [info] Connecting to the target slave host 192.168.123.14, running recover script..
 Wed Jun  6 14:51:37 2012 - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user=root --slave_host=192.168.123.14 --slave_ip=192.168.123.14  --slave_port=3306 --apply_files=/var/tmp/saved_master_binlog_from_192.168.123.13_3306_20120606145135.binlog --workdir=/var/tmp --target_version=5.5.25-log --timestamp=20120606145135 --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.52 --slave_pass=xxx
 Wed Jun  6 14:51:37 2012 - [info] 
 Applying differential binary/relay log files /var/tmp/saved_master_binlog_from_192.168.123.13_3306_20120606145135.binlog on 192.168.123.14:3306. This may take long time...
 Applying log files succeeded.
 Wed Jun  6 14:51:37 2012 - [info]  All relay logs were successfully applied.
 Wed Jun  6 14:51:37 2012 - [info] Getting new master's binlog name and position..
 Wed Jun  6 14:51:37 2012 - [info]  mysql-bin.000023:107
 Wed Jun  6 14:51:37 2012 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.123.14', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000023', MASTER_LOG_POS=107, MASTER_USER='r_test', MASTER_PASSWORD='xxx';
 Wed Jun  6 14:51:37 2012 - [warning] master_ip_failover_script is not set. Skipping taking over new master ip address.
 Wed Jun  6 14:51:37 2012 - [info] ** Finished master recovery successfully.
 Wed Jun  6 14:51:37 2012 - [info] * Phase 3: Master Recovery Phase completed.
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] * Phase 4: Slaves Recovery Phase..
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] Generating relay diff files from the latest slave succeeded.
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] All new slave servers recovered successfully.
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] * Phase 5: New master cleanup phease..
 Wed Jun  6 14:51:37 2012 - [info] 
 Wed Jun  6 14:51:37 2012 - [info] Resetting slave info on the new master..
 Wed Jun  6 14:51:37 2012 - [info] Master failover to 192.168.123.14(192.168.123.14:3306) completed successfully.
 Wed Jun  6 14:51:37 2012 - [info]
 
----- Failover Report -----
 
app1: MySQL Master failover 192.168.123.13 to 192.168.123.14 succeeded
 
Master 192.168.123.13 is down!
 
Check MHA Manager logs at dg55.yang.com:/masterha/app1/manager.log for details.
 
Started automated(non-interactive) failover.
 The latest slave 192.168.123.14(192.168.123.14:3306) has all relay logs for recovery.
 Selected 192.168.123.14 as a new master.
 192.168.123.14: OK: Applying all logs succeeded.
 Generating relay diff files from the latest slave succeeded.
 192.168.123.14: Resetting slave info succeeded.
 Master failover to 192.168.123.14(192.168.123.14:3306) completed successfully.
 		
  

 

 

 

3：在原从库192.168.123.14上查看结果
 

 

     
 
  1. mysql> show master status;  
    2.  
 
  2. +------------------+----------+--------------+------------------+  
    3.  
 
  3. | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |  
    4.  
 
  4. +------------------+----------+--------------+------------------+  
    5.  
 
  5. | mysql-bin.000023 |      107 | bbs,test     | mysql            |  
    6.  
 
  6. +------------------+----------+--------------+------------------+  
    7.  
 
  7. 1 row in set (0.00 sec)  
    8.  
 
  8.  
    9.  
 
  9.  mysql> show slave status\G;   
    10.  
 
  10. *************************** 1. row ***************************  
    11.  
 
  11.                Slave_IO_State:   
    12.  
 
  12.                   Master_Host: 192.168.123.13  
    13.  
 
  13.                   Master_User: r_test  
    14.  
 
  14.                   Master_Port: 3306  
    15.  
 
  15.                 Connect_Retry: 60  
    16.  
 
  16.               Master_Log_File:   
    17.  
 
  17.           Read_Master_Log_Pos: 4  
    18.  
 
  18.                Relay_Log_File: dg54-relay-bin.000001  
    19.  
 
  19.                 Relay_Log_Pos: 4  
    20.  
 
  20.         Relay_Master_Log_File:   
    21.  
 
  21.              Slave_IO_Running: No  
    22.  
 
  22.             Slave_SQL_Running: No  
    23.  
 
  23.               Replicate_Do_DB:   
    24.  
 
  24.           Replicate_Ignore_DB:   
    25.  
 
  25.            Replicate_Do_Table:   
    26.  
 
  26.        Replicate_Ignore_Table:   
    27.  
 
  27.       Replicate_Wild_Do_Table:   
    28.  
 
  28.   Replicate_Wild_Ignore_Table:   
    29.  
 
  29.                    Last_Errno: 0  
    30.  
 
  30.                    Last_Error:   
    31.  
 
  31.                  Skip_Counter: 0  
    32.  
 
  32.           Exec_Master_Log_Pos: 0  
    33.  
 
  33.               Relay_Log_Space: 126  
    34.  
 
  34.               Until_Condition: None  
    35.  
 
  35.                Until_Log_File:   
    36.  
 
  36.                 Until_Log_Pos: 0  
    37.  
 
  37.            Master_SSL_Allowed: No  
    38.  
 
  38.            Master_SSL_CA_File:   
    39.  
 
  39.            Master_SSL_CA_Path:   
    40.  
 
  40.               Master_SSL_Cert:   
    41.  
 
  41.             Master_SSL_Cipher:   
    42.  
 
  42.                Master_SSL_Key:   
    43.  
 
  43.         Seconds_Behind_Master: NULL  
    44.  
 
  44. Master_SSL_Verify_Server_Cert: No  
    45.  
 
  45.                 Last_IO_Errno: 0  
    46.  
 
  46.                 Last_IO_Error:   
    47.  
 
  47.                Last_SQL_Errno: 0  
    48.  
 
  48.                Last_SQL_Error:   
    49.  
 
  49.   Replicate_Ignore_Server_Ids:   
    50.  
 
  50.              Master_Server_Id: 1  
    51.  
 
  51. 1 row in set (0.00 sec)  
    52.  
 
  52.  
    53.  
 
  53. ERROR:   
    54.  
 
  54. No query specified 
    55.  

 

备注：本文只简单记录了mha的环境部署过程，更多高级的内容，例如配合keepalive使用VIP，让客户端连接数据库透明化以及手动failover和master_ip_failover_script脚本，半同步复制等功能后续将继续研究！
 

参考文章，感谢作者分享
http://who0168.blog.51cto.com/253401/699030
http://huoding.com/2011/12/18/139
http://www.vmcd.org/2012/04/mysql-high-availability-mha/
 

本文转自斩月博客51CTO博客，原文链接http://blog.51cto.com/ylw6006/890360如需转载请自行联系原作者
 


 

ylw6006

                        
                    

                    
                        

                            

    
文章标签：

    

        

            云数据库 RDS MySQL 版
        

        

            关系型数据库
        

        

            MySQL
        

        

            网络安全
        

        

            数据库
        

    



                            

    
关键词：

    

        

            云数据库 RDS MySQL 版部署
        

        

            云数据库 RDS MySQL 版部署mha
        

    



                            
                        

                        

    
相关实践学习

    

        

            
如何在云端创建MySQL数据库

            

                
开始实验后，系统会自动创建一台自建MySQL的 源数据库 ECS 实例和一台 目标数据库 RDS。

                
            

        

        

            
全面了解阿里云能为你做什么

            

                
阿里云在全球各地部署高效节能的绿色数据中心，利用清洁计算为万物互联的新世界提供源源不断的能源动力，目前开服的区域包括中国（华北、华东、华南、香港）、新加坡、美国（美东、美西）、欧洲、中东、澳大利亚、日本。目前阿里云的产品涵盖弹性计算、数据库、存储与CDN、分析与搜索、云通信、网络、管理与监控、应用服务、互联网中间件、移动服务、视频服务等。通过本课程，来了解阿里云能够为你的业务带来哪些帮助 &nbsp; &nbsp; 相关的阿里云产品：云服务器ECS 云服务器 ECS（Elastic Compute Service）是一种弹性可伸缩的计算服务，助您降低 IT 成本，提升运维效率，使您更专注于核心业务创新。产品详情: https://www.aliyun.com/product/ecs

                
            

        

    



                        
                    
                

                


                

                    

                        

                            
                                
                            
                            

                        

                        科技探索者
                        

                        

                    

                    

                        

                            

                            
目录

                        

                        

                    

                

                

                    

                


                

    
相关文章

    

        

            

                

                    1288912195458132
                    
                

                |
                
3月前

                |
                

                    Kubernetes
                    关系型数据库
                    MySQL
                

            

            

                

                    
                        k8s快速部署MySQL单机 
                    
                    
k8s快速部署MySQL单机 


                    

                        

                            

                                1288912195458132
                                
                            

                            42
                            1
                            
                        

                    

                

                
            

        

        

            

                

                    杀死一只知更鸟debug
                    
                

                |
                
2月前

                |
                

                    关系型数据库
                    MySQL
                    数据安全/隐私保护
                

            

            

                

                    
                        docker应用部署---MySQL的部署配置
                    
                    
这篇文章介绍了如何使用Docker部署MySQL数据库，包括搜索和拉取MySQL镜像、创建容器并设置端口映射和目录映射、进入容器操作MySQL，以及如何使用外部机器连接容器中的MySQL。


                    

                        

                            

                                杀死一只知更鸟debug
                                
                            

                            442
                            1
                            
                        

                    

                

                
                    docker应用部署---MySQL的部署配置
                
            

        

        

            

                

                    yuanzhengme
                    
                

                |
                
1月前

                |
                

                    关系型数据库
                    MySQL
                    数据库
                

            

            

                

                    
                        使用Docker部署的MySQL数据库，数据表里的中文读取之后变成问号，如何处理？
                    
                    
【10月更文挑战第1天】使用Docker部署的MySQL数据库，数据表里的中文读取之后变成问号，如何处理？

                    

                        

                            

                                yuanzhengme
                                
                            

                            54
                            3
                            
                        

                    

                

                
            

        

        

            

                

                    yuanzhengme
                    
                

                |
                
1月前

                |
                

                    关系型数据库
                    MySQL
                    数据库
                

            

            

                

                    
                        使用Docker部署的MySQL数据库如何设置忽略表名大小写？
                    
                    
【10月更文挑战第1天】使用Docker部署的MySQL数据库如何设置忽略表名大小写？

                    

                        

                            

                                yuanzhengme
                                
                            

                            96
                            1
                            
                        

                    

                

                
            

        

        

            

                

                    qhhf_地道酬勤
                    
                

                |
                
2月前

                |
                

                    NoSQL
                    关系型数据库
                    Redis
                

            

            

                

                    
                        mall在linux环境下的部署（基于Docker容器），Docker安装mysql、redis、nginx、rabbitmq、elasticsearch、logstash、kibana、mongo
                    
                    
mall在linux环境下的部署（基于Docker容器），docker安装mysql、redis、nginx、rabbitmq、elasticsearch、logstash、kibana、mongodb、minio详细教程，拉取镜像、运行容器

                    

                        

                            

                                qhhf_地道酬勤
                                
                            

                            476
                            3
                            
                        

                    

                

                
                    mall在linux环境下的部署（基于Docker容器），Docker安装mysql、redis、nginx、rabbitmq、elasticsearch、logstash、kibana、mongo
                
            

        

        

            

                

                    Codelinghu
                    
                

                |
                
1月前

                |
                

                    存储
                    关系型数据库
                    MySQL
                

            

            

                

                    
                        【MySQL精装典藏版】MySQL的安装与部署
                    
                    
【MySQL精装典藏版】MySQL的安装与部署

                    

                        

                            

                                Codelinghu
                                
                            

                            48
                            0
                            
                        

                    

                

                
            

        

        

            

                

                    yuanzhengme
                    
                

                |
                
1月前

                |
                

                    关系型数据库
                    MySQL
                    数据库
                

            

            

                

                    
                        如何使用Docker部署MySQL数据库？
                    
                    
【10月更文挑战第1天】如何使用Docker部署MySQL数据库？

                    

                        

                            

                                yuanzhengme
                                
                            

                            159
                            0
                            
                        

                    

                

                
            

        

        

            

                

                    尹正杰
                    
                

                |
                
2月前

                |
                

                    存储
                    关系型数据库
                    MySQL
                

            

            

                

                    
                        使用Docker快速部署Mysql服务器
                    
                    
本文介绍了如何使用Docker快速部署MySQL服务器，包括下载官方MySQL镜像、启动容器、设置密码、连接MySQL服务器以及注意事项。

                    

                        

                            

                                尹正杰
                                
                            

                            428
                            18
                            
                        

                    

                

                
            

        

        

            

                

                    pbeskoyq7ffm4
                    
                

                |
                
3月前

                |
                

                    关系型数据库
                    MySQL
                    测试技术
                

            

            

                

                    
                        使用docker部署MySQL测试环境
                    
                    
使用docker部署MySQL测试环境

                    

                        

                            

                                pbeskoyq7ffm4
                                
                            

                            42
                            0
                            
                        

                    

                

                
            

        

        

            

                

                    pbeskoyq7ffm4
                    
                

                |
                
3月前

                |
                

                    固态存储
                    关系型数据库
                    MySQL
                

            

            

                

                    
                        mysql多实例一键部署
                    
                    
mysql多实例一键部署

                    

                        

                            

                                pbeskoyq7ffm4
                                
                            

                            31
                            0
                            
                        

                    

                

                
            

        

    



            

            

                
                
                    
                    

    

        

            
热门文章

        

        

            
最新文章

        

    

    

        

            

                
  • 
                    
                        
    
                            
    1
    
                            
                            
    测试开启MySQL performance_schema后对性能的影响
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
    2
    
                            
                            
    MySQL调优之服务器参数优化实践
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
    3
    
                            
                            
    Mysql5注射技巧总结
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    4
    
                            
    mysql左关联不走索引的一个问题的排查过程及思考
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    5
    
                            
    应用MySQL MGR
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    6
    
                            
    mysql修改用户密码
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    7
    
                            
    如何修改WAMP中mysql默认空密码
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    8
    
                            
    MySQL-5.5.33主从复制
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    9
    
                            
    mysql的总结6--视图的学习
    
                            
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    10
    
                            
    删除MySQL重复数据
    
                            
    
                        
    
                        
                
    • 
            
    
            
    
                
            
    
        
    
        
    
            
    
                
  • 
                    
                        
    
                            
    1
    
                            
                            
    MySQL上亿数据查询优化：实践与技巧
    
                            
    275
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
    2
    
                            
                            
    如何理解Mysql的索引及他们的原理--------二叉查找树和平衡二叉树和B树和B+树
    
                            
    46
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
    3
    
                            
                            
    MySQL：union all与union区别详解
    
                            
    85
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    4
    
                            
    学习mysql中使用inner join，left join 等
    
                            
    47
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    5
    
                            
    【最佳实践】MySQL数据库迁移到PXC集群
    
                            
    85
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    6
    
                            
    MySQL PXC集群配置IPv6
    
                            
    45
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    7
    
                            
    【实操记录】MySQL主从配置
    
                            
    131
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    8
    
                            
    【实操记录】MySQL二进制安装包部署
    
                            
    176
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    9
    
                            
    mysql模糊查询指定根据第几个字符来匹配
    
                            
    225
    
                        
    
                        
                
    • 
                
  • 
                    
                        
    
                            
                            
    10
    
                            
    mysql使用 CONCAT(字段,字段) 函数拼接
    
                            
    59
    
                        
    
                        
                
    • 
            
    
            
    
                
            
    
        
    
    
    

    
                    
                    
    
    
    
        
    相关课程
    
        更多
    
    
    
    
        
  • 
                MySQL企业常见架构与调优经验分享
            
    • 
        
  • 
                云数据库MySQL版快速上手教程
            
    • 
        
  • 
                阿里云云原生数据仓库AnalyticDB MySQL版  使用教程
            
    • 
        
  • 
                MySQL实战进阶
            
    • 
        
  • 
                数据库及SQL/MySQL基础
            
    • 
        
  • 
                云数据库MySQL快速入门
            
    • 
    
    

    
                    
    
    
    
        
    相关电子书
    
        更多
    
    
    
    
        
  • 
                搭建电商项目架构连接MySQL
            
    • 
        
  • 
                搭建4层电商项目架构，实战连接MySQL
            
    • 
        
  • 
                PolarDB MySQL引擎重磅功能及产品能力盛大发布
            
    • 
    
    

    
                    
    
    
    
        
    相关实验场景
    
        更多
    
    
    
    
        
  • 
            灵活弹性的PolarDB Serverless确保数据业务持续在线
        
    • 
        
  • 
            云端MySQL的安装及应用
        
    • 
        
  • 
            体验PolarDB MySQL多主集群
        
    • 
        
  • 
            基于ECS+RDS的在线留言系统
        
    • 
        
  • 
            PolarDB MySQL HTAP：实时数据分析加速
        
    • 
        
  • 
            MySQL数据库DTS迁移上云
        
    • 
    
    

    
                    
                    
    
    
    
        
    推荐镜像
    
        更多
    
    
    
    
        
  • 
            mysql
        
    • 
        
  • 
            mariadb
        
    • 
        
  • 
            mongodb
        
    • 
    
    

    
                    
    
                        
    
    
    
        
    下一篇
    
    
    
    DataWorks售前咨询