Please, don't use the command line to configure MySQL master-slave replication. Isn't it fragrant to deploy with urlos interface?

since URLOS-2.2.1 Version added mysql After the master-slave cluster , Users can easily create mysql Master-slave cluster （ One master, many followers ）, There's no command line , Simple and easy to maintain .

One 、 Introduce

The database is based on MySQL-5.7 The database master-slave cluster , Its use is mainly reflected in two aspects ：

1.1 Master slave copy

Build a database environment exactly like the main database , Called from database . The main database is usually a real-time business database , Generally speaking, there are ：

1. As a backup database , After the main database server fails , Switch to continue working from database ;

2. It can be backed up from the database 、 Data statistics, etc , This does not affect the performance of the primary database .

1.2 Read / write separation

It means that different databases are used for reading and writing , Read and write databases are deployed on different servers ; Generally, the database environment for reading and writing is configured as , A written database , One or more read databases , Each database is located on different servers , Make full use of server performance and database performance ; Therefore, it will involve how to ensure the data consistency of reading and writing databases , At this time, it can be realized by master-slave replication technology .

Two 、 applications

The business throughput is very large , Read database （ It can be simply understood as the proportion and influence of ） It's a big load .

3、 ... and 、 Deployment method

step 1： Deploy the master database service

stay A Deployment on host MySQL-5.7, As the main database , Service name such as ：mysql57001_master

stay 【 Set up 】 Lieutenant general Binary log format choice ROW, Required here ！

step 2： Shut down the primary database

After the master database is deployed , Turn it off ：

step 3： Package the master database file

Enter the file management tool of the main database ：

Enter into data Catalog ：

take mysql57001_master directories ：

After packing , Restart the main database .

step 4： Deploy the slave database service

stay B Deployment on host MySQL-5.7, As a slave database , Pay attention to the difference between the service names of the master and slave databases ：

stay 【 Set up 】 Lieutenant general Binary log format choice ROW, It is recommended that the format be consistent with the main database ！

step 5： Overwrite the slave database with the master database file

Before coverage , First close the slave database ：

Overwrite the slave database file with the previously packaged master database file ：

Then set the current permission of the slave database file to “777”：

Last , Restart from database ：

thus ,MySQL The master-slave cluster is deployed , There is no limit to the number of slave databases , You can add multiple MySQL From database , In order to meet the needs of high concurrency business .