The key to setting up MySQL master-slave replication is configuration synchronization, permission allocation and network interoperability. 1. Preparation includes ensuring that the two MySQL instances are running normally, with the same version, clear IP, and opening the 3306 port and firewall settings; 2. To configure the main library, you need to enable binary logs, set a unique server-id, create a copy account and authorize it, and record the file and Position of the main library status; 3. To configure the slave library, you need to set different server-ids, configure relay logs, connect to the main library and start the replication process; 4. For FAQ troubleshooting, you should check the network, user permissions, server-id uniqueness, binlog and relay log settings and password correctness, combined with error information positioning problems in SHOW SLAVE STATUS. As long as you pay attention to these key points, the master-slave copy setting can be completed smoothly.
MySQL master-slave replication settings are not difficult, but there are many details. The key points are configuration synchronization between the master library and the slave library, correct permission allocation, and network interoperability. As long as you figure out these points, the rest is to follow the steps.

1. Preparation: Confirm the basic environment
Before you start, make sure you already have two MySQL instances, one as the master and one as the slave. They can communicate with each other and the versions should be consistent or compatible as much as possible.
- The IP address of the master and slave server is clear, for example, the master library is
192.168.1.10
, and the slave library is192.168.1.11
- MySQL service has been installed and run normally
- If you have a firewall, remember to open port 3306 and a dedicated port for replication (the default is also 3306)
If you are using a cloud server, you also need to check whether the security group releases these connections.

2. Configure the main library (Master)
First, enable binary logs on the main library and set a unique server-id. This ID cannot be repeated with other MySQL instances.
Modify the configuration file of the main library (usually /etc/my.cnf
or /etc/mysql/my.cnf
):

[mysqld] server-id=1 log-bin=mysql-bin bind-address = 0.0.0.0 # Allow external access
After saving, restart MySQL service:
sudo systemctl restart mysql
Then create an account dedicated to copying and authorize:
CREATE USER 'replica'@'%' IDENTIFIED BY 'your_password'; GRANT REPLICATION SLAVE ON *.* TO 'replica'@'%'; FLUSH PRIVILEGES;
Finally, check the status of the current main library and record the values of File and Position:
SHOW MASTER STATUS;
3. Configure the slave library (Slave)
Also, you need to modify the configuration file of the slave library and set different server-ids, such as 2:
[mysqld] server-id=2 relay-log=mysqld-relay-bin bind-address = 0.0.0.0
After restarting the MySQL service, enter the MySQL command line and execute the following command to connect to the main library:
CHANGE MASTER TO MASTER_HOST='192.168.1.10', MASTER_USER='replica', MASTER_PASSWORD='your_password', MASTER_LOG_FILE='mysql-bin.000001', -- This is filled in MASTER_LOG_POS= 4 according to the previous SHOW MASTER STATUS result; -- Also replace with the actual value
Start the replication process:
START SLAVE;
Check if the status is normal:
SHOW SLAVE STATUS\G
Focus on whether Slave_IO_Running
and Slave_SQL_Running
are both Yes.
4. Frequently Asked Questions and Troubleshooting Suggestions
Sometimes it is set up but still cannot connect from the library. Common reasons include:
- The network is not connected or the firewall is not open to port 3306
- The user permissions are incorrect, especially the host part is written incorrectly
- The server-id is repeated, the master and slave must be different
- The main library does not have binlog enabled, or the slave library does not have relay log provided
- Password is written wrong, especially special characters are not escaped
If an error occurs, first look at the Last_Error
field in SHOW SLAVE STATUS\G
, which can generally locate the problem.
Basically that's it. The whole process is not complicated, but it is easy to ignore some places, such as server-id, user permissions, network settings, etc. As long as you take it step by step, most problems can be solved.
The above is the detailed content of how to set up mysql master slave replication. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
