MySQL master-slave replication data synchronization, summary of common problems

Hello everyone , I meet you again , I'm the king of the whole stack .

One 、 Problem description ：

When we configure MySQL Main synchronization , Yes, master synchronization can be realized , But after restarting the machine or for other reasons MySQL Can't sync .

Two 、Slave Two key processes

mysql replication in slave There are two key processes on the machine , No one can die , One is slave_sql_running, One is Slave_IO_Running, One responsible for communicating with the host io signal communication , A person in charge of his own slave mysql process .

3、 ... and 、 If it is Slave_SQL_Running：no：

The solution is as follows ：

MariaDB [(none)]> stop slave;                                                      
MariaDB [(none)]> SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;            
MariaDB [(none)]> start slave;                                                      
MariaDB [(none)]> show slave status\G

Copy

Four 、 If it is slave_io_running：no

The solution is as follows ：

1、 Look at the master server

MariaDB [(none)]> show master status\G

Copy

2、 View... From the server

The problem ： Find out Master_Log_File No corresponding .

3、 appear Slave_IO_Running: No Operation on the machine

MariaDB [(none)]> slave stop;                 
MariaDB [(none)]>CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000026', MASTER_LOG_POS=0;  
MariaDB [(none)]> slave start;                               
MariaDB [(none)]> show slave status\G

Copy

This problem will be solved ！

Publisher ： Full stack programmer stack length , Reprint please indicate the source ：https://javaforall.cn/111543.html Link to the original text ：https://javaforall.cn