Shulou(Shulou.com)06/01 Report--

Let me tell you a little bit about the installation and configuration process of the MMM high-availability architecture in MySQL. Have you learned about similar topics before? If you are interested, let's take a look at this article. I believe it will be of some help to you after reading the installation and configuration process of the MMM high-availability architecture in MySQL.

Experimental environment

Host IP address mysql-m1 Master CVM 192.168.58.131mysql-m2 Master CVM 192.168.58.136mysql-m3 Slave CVM 192.168.58.146mysql-m4 Slave CVM 192.168.58.147mysql-monitor Monitoring proxy CVM 192.168.58.148 Experimental process to build MySQL multi-master and multi-slave mode

1. Install MySQL on all four MySQL CVMs, omitting the process.

2. Configure the ALI cloud source, and then install the epel-rlease source to install the mysql-mmm tool kit below.

[root@localhost ~] # wget-O / etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-7.repo[root@localhost ~] # yum-y install epel-release [root@localhost ~] # yum clean all & & yum makecache

3. Configuration modification M1 main configuration file.

Vim / etc/my.cnf [mysqld] log_error=/var/lib/mysql/mysql.err # configuration error log = / var/lib/mysql/mysql_log.log # configuration common log log _ slow_queries=/var/lib/mysql_slow_queris.log # configure slow log binlog-ignore-db=mysql Information_schema # configure a database that does not need to record binary logs character_set_server=utf8 # configure character set log_bin=mysql_bin # enable binlog logs for master-slave data replication server_id=1 # each server -the value of id cannot be the same log_slave_updates=true # this database is down Standby database takeover sync_binlog=1 # allows synchronous binary log auto _ increment_increment=2 # fields to be incremented in turn how many auto_increment_offset=1 # starting values of the increment field: odd ID such as 1, 3, 5, etc.

After no problem with the configuration, copy the configuration file to another primary cloud server

[root@localhost ~] # scp / etc/my.cnf root@192.168.58.136:/etc/

4. Configure mysql-m1 and mysql-m2 main mode

First look at the location of the log bin log and the posvalue.

[root@localhost1] # mysqlWelcome to the MariaDB monitor. Commands end with; or\ g.Your MySQL connection id is 1065Server version: 5.5.24-log Source distributionCopyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others.Type 'help;' or'\ h' for help. Type'\ c'to clear the current input statement.MySQL [(none)] > show master status +-- + | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +-- -+ | mysql_bin.000002 | 107 | | mysql Information_schema | +-+ 1 row in set (0.00 sec) [root@localhost2 ~] # mysqlWelcome to the MariaDB monitor. Commands end with; or\ g.Your MySQL connection id is 1065Server version: 5.5.24-log Source distributionCopyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others.Type 'help;' or'\ h' for help. Type'\ c'to clear the current input statement.MySQL [(none)] > show master status +-- + | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +-- -+ | mysql_bin.000002 | 107 | | mysql Information_schema | +-- + 1 row in set (0.00 sec)

Then, mysql-m1 and mysql-m2 elevate access to each other.

Mysql-m1MySQL [(none)] > grant replication slave on *. * to 'replication'@'192.168.58.%' identified by' 123456; MySQL [(none)] > change master to master_host='192.168.58.136',master_user='replication',master_password='123456',master_log_file='mysql_bin.000002',master_log_pos=107;MySQL [(none)] > flush privileges Mysql-m2MySQL [(none)] > grant replication slave on *. * to 'replication'@'192.168.58.%' identified by' 123456; MySQL [(none)] > change master to master_host='192.168.58.131',master_user='replication',master_password='123456',master_log_file='mysql_bin.000002',master_log_pos=107;MySQL [(none)] > flush privileges

Finally, check the master-slave status of mysql-m1 and mysql-m2 CVM respectively, and mainly view

Slave_IO_Running: Yes

Slave_SQL_Running: Yes .

MySQL [(none)] > start slave;MySQL [(none)] > show slave status\ G * * 1. Row * * Slave_IO_State: Waiting for master to send event Master_Host: 192.168.58.131 Master_User: replication Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql_bin.000002 Read_Master_Log_Pos: 107 Relay_Log_File: localhost-relay-bin.000012 Relay_Log_Pos: 253 Relay_Master_Log_File: mysql_bin.000002 Slave_IO_Running: Yes Slave_SQL_Running: Yes

Indicates that the master synchronization configuration is successful.

Test master master synchronization, create a new library test01 in mysql-m1

Mysql-m1MySQL [(none)] > create database test01;MySQL [(none)] > show databases +-+ | Database | +-+ | information_schema | | # mysql50#.mozilla | | bbs | | mysql | | performance_schema | | test | | test01 | +-+ 7 rows In set (0.22sec) mysql-m2 # successfully tested MySQL [(none)] > show databases +-+ | Database | +-+ | information_schema | | # mysql50#.mozilla | | mysql | | performance_schema | | test | | test01 | +-+ 7 rows in set (0.22 sec)

5. Configure myqsl-m3 and mysql-m4 as slave libraries of mysql-m1.

First, copy the / etc/my.cnf file on mysql-m1 to myqsl-m3 and mysql-m4 CVM.

Mysql-m1 [root@localhost ~] # scp / etc/my.cnf root@192.168.58.146:/etc/ [root@localhost ~] # scp / etc/my.cnf root@192.168.58.147:/etc/

View the status values of the database in mysql-m1.

MySQL [(none)] > show master status +-- + | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +-- -+ | mysql_bin.000002 | 107 | | mysql Information_schema | +-- + 1 row in set (0.00 sec)

Execute on mysql-m3 and mysql-m4 respectively.

Mysql-m3MySQL [(none)] > change master to master_host='192.168.58.131',master_user='replication',master_password='123456',master_log_file='mysql_bin.000002',master_log_pos=107;mysql-m4MySQL [(none)] > change master to master_host='192.168.58.131',master_user='replication',master_password='123456',master_log_file='mysql_bin.000002',master_log_pos=107

Check the master / slave status of mysql-m3 and mysql-m4 CVM respectively, as shown below.

MySQL [(none)] > show slave status\ G * * 1. Row * * Slave_IO_State: Waiting for master to send event Master_Host: 192.168.58.131 Master_User: replication Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql_bin.000002 Read_Master_Log_Pos: 107 Relay_Log_File: localhost-relay-bin.000012 Relay_Log_Pos: 253 Relay_Master_Log_File: mysql_bin.000002 Slave_IO_Running: Yes Slave_SQL_Running: Yes installation and configuration MySQL-MMM

There is no mysql-mmm package for CentOS by default. Since our official epel source has been installed before, we have to install MMM on all five hosts.

[root@localhost ~] # yum-y install mysql-mmm*

After installation, configure MMM

[root@localhost mongodb1] # vim / etc/mysql-mmm/mmm_common.conf cluster_interface ens33 # Nic name. Replication_user replication replication_password 123456 agent_user mmm_agent agent_password 123456 ip 192.168.58.131 mode master peer db2 ip 192.168.58.136 mode master peer db1 ip 192.168.58.146 mode slave ip 192.168.58.147 mode slave hosts db1, db2 ips 192.168.58.100 mode exclusive hosts db3 Db4 ips 192.168.58.200 192.168.58.210 mode balanced # copy the configuration file to the directory corresponding to several other database CVM [root@localhost mysql-mmm] # scp mmm_common.conf root@192.168.58.136:/etc/mysql-mmm/ [root@localhost mysql-mmm] # scp mmm_common.conf root@192.168.58.146:/etc/mysql-mmm/ [root@localhost mysql-mmm] # scp Mmm_common.conf root@192.168.58.147:/etc/mysql-mmm/ [root@localhost mysql-mmm] # scp mmm_common.conf root@192.168.58.148:/etc/mysql-mmm/

Configure on a terminal that is a monitor CVM

Cd / etc/mysql-mmm/ # change password vim mmm_mon.conf monitor_user mmm_monitor monitor_password 123456

Authorize mmm_agent on all databases

MySQL [(none)] > grant super, replication client, process on *. * to 'mmm_agent'@'192.168.58.%' identified by' 123456 authorization for mmm_agent

Authorize mmm_moniter on all databases

MySQL [(none)] > grant replication client on *. * to 'mmm_monitor'@'192.168.58.%' identified by' 123456 permission setting for mmm_monitor authorization MySQL [(none)] > flush privileges# refresh permission settings

Modify the mmm_agent.conf of all databases

[root@localhost mysql-mmm] # vim / etc/mysql-mmm/mmm_agent.confinclude 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, and have the# proper IP addresses set in mmm_common.conf.this db1 # are set to db1,db2,db3,db4~ on four database CVM respectively

Start mysql-mmm-agent on all database cloud servers

[root@localhost mysql-mmm] # systemctl start mysql-mmm-agent.service# start mmm-agent Service [root@localhost mysql-mmm] # systemctl enable mysql-mmm-agent.service# Settings mmm-agent Service Boot

Configure on monitor CVM

[root@localhost mysql-mmm] # cd / etc/mysql-mmm/ [root@localhost mysql-mmm] # vim mmm_mon.conf ip 127.0.0.1 pid_path / run/mysql-mmm-monitor.pid bin_path / usr/libexec/mysql-mmm status_path / var/lib/mysql-mmm/mmm_mond.status ping_ips 192 .168.58.131192.168.58.136192.168.58.146192.168.58.147 # specify the supervised IP address of CVM auto_set_online 10 # The kill_host_bin does not exist by default Though the monitor will # throw a warning about it missing. See the section 5.10 "Kill Host # Functionality" in the PDF documentation. # # kill_host_bin / usr/libexec/mysql-mmm/monitor/kill_host # monitor_user mmm_monitor # set the supervision account monitor_password 123456 # set the supervision password [root@localhost mysql-mmm] # systemctl start mysql-mmm-monitor.service # launch mysql-mmm-monitor [root@localhost mysql-mmm] # mmm_control show # View the operation of the node db1 (192.168.58.131) master/ONLINE. Roles: writer (192.168.58.100) db2 (192.168.58.136) master/ONLINE. Roles: db3 (192.168.58.146) slave/ONLINE. Roles: reader (192.168.58.200) db4 (192.168.58.147) slave/ONLINE. Roles: reader (192.168.58.210)

When we stop the mysql service of mysql-m3, the corresponding VIP will be automatically bound to mysql-m4

[root@localhost mysql-mmm] # mmm_control show db1 (192.168.58.131) master/ONLINE. Roles: writer (192.168.58.100) db2 (192.168.58.136) master/ONLINE. Roles: db3 (192.168.58.146) slave/HARD_OFFLINE. Roles:

Db4 (192.168.58.147) slave/ONLINE. Roles: reader (192.168.58.210) (192.168.58.200)

What do you think of this article on the installation and configuration process of MMM high-availability architecture in MySQL? If you want to know more about it, you can continue to follow our industry information section.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.