Latency of master-slave replication in mysql _ MySQL

Problem about master/slave replication delay in mysql bitsCN.com
When I interviewed mysqldba about the master-slave replication delay in mysql, I encountered a question: describes the implementation principle of the msyql replication mechanism and how to keep dropping the mysql master database, restore the database node of the slave with inconsistent data?
MySQL replication is an asynchronous replication, from one MySQL instace (called Master) to another MySQL instance (called Slave ). The entire replication operation is completed by three processes, two of which are on Slave (SQL process and IO process), and the other on Master (IO process. By referencing a Sina Daniel, mysql replication is a single-thread asynchronous replication process based on binlog. The basic process of MySQL Replication is as follows: 1. the IO process on the Slave connects to the Master and requests the log content after the specified location of the log file (or from the initial log;
[Html] mysql> change master to-> MASTER_HOST = 'master _ host_name ',-> MASTER_USER = 'replication _ user_name',-> MASTER_PASSWORD = 'replication _ password ', -> MASTER_LOG_FILE = 'recorded _ log_file_name ',-> MASTER_LOG_POS = recorded_log_position; 2. after the Master receives a request from the Slave IO process, the IO process responsible for replication reads the log information after the specified location of the log based on the request information and returns it to the Slave IO process. Besides the information contained in the log, the returned information also includes the name of the bin-log file on the Master end and the location of the bin-log; 3. after the Slave IO process receives the information, add the received log content to the end of the relay-log file on the Slave end in sequence, and record the file name and location of the bin-log on the Master end to the master-info file, so that the next read can clearly show the high-speed Master "I need to start from the location of a bin-log, please send it to me "; 4. after the Slave SQL process detects the newly added content in relay-log, it will immediately parse the relay-log content into the executable content during actual execution on the Master end, perform the following operations on your own: (1) log on to the master server and check the status of the master server: mysql> show master status; find the data offset value of the current master. (2) log on to the slave server and perform the synchronization operation. [Code] mysql> stop slave; mysql> change master to directly locate this worthy position; this is equivalent to specifying the corresponding location for slave. Mysql> start slave; (3) view status from the server mysql> show slave status http://blog.csdn.net/chen861201/article/details/8022501bitsCN.com