MySQL Slave data re-replication example

MySQL Slave data re-replication: an alert message indicating a synchronization error occurred on a server Load balancer instance. The SQL THREAD of the Server Load balancer instance is stopped and the status is as follows: 01 mysql> show slave status \ G02 03... 04 05 Slave_IO_Running: Yes06 Slave_ SQL _Running: No07 www.2cto.com 08... 09 10 Last_Errno: 105011 Last_Error: Error 'table 'temp _ T3 'already exists' on query. default database: 'xxxx '. query: 'create TABLE TEMP_T3 (id varchar (30) '12 Skip_Counter: 013 Exec_Master_Log_Pos: 5530696414... according to the above information A temporary data processing table created on aster already exists on Slave. This is a coincidence: I usually make data processing tables on slave, which may result in inconsistent M/S data (non-Online production data is affected ), however, the processing pressure of some masters can be shared. As the services undertaken by this Master have been deprecated today, data processing on the Master directly causes this error. The solution is as follows: 1. stop slave1mysql> stop slave; 2. delete the conflicting table www.2cto.com 1 mysql> drop table TEMP_T3; 3. change log position1mysql> change master to MASTER_HOST = '... ', 2 MASTER_USER = '... ', 3 MASTER_PASSWORD = '... ', 4 MASTER_PORT = ..., 5 MASTER_LOG_FILE = '... ', 6 MASTER_LOG_POS = 55306964; 'master _ LOG_POS' value: 'exec _ Master_Log_Pos 'value 4. enable the slave thread www.2cto.com 1 mysql> start slave; 5. check status 1... 2 3 Slave_IO_Running: Yes4 Slave_ SQL _Running: Yes5
6... the key of the author Wang Zi