mysql replication recover from the master

Backup and Recovery

1. From the database query status

slave status

Master_Log_File: mysql-bin.000120

Slave_IO_Running: Yes

Slave_SQL_Running: No

RELAY_Master_Log_FILE: mysql-bin.000119

Exec_Master_Log_Pos: 87663322

Last_Error: xxxxx

This state is from mysql-bin.000119 of 87,663,322 lines began to recover, only a little more than right.

2. The main database query binlog

show binlog events in 'mysql-bin.000119 ' from 87663322 limits 100000;
then see a card on which a transaction.

3. Skip the wrong business from library

Slave STOP;
the SET GLOBAL SLAVE_SLAVE_SKIP_COUNTER = 1;
Start Slave;
then keep looking back to step 1. If each transaction is not long, you can adjust the value of SLAVE_SLAVE_SKIP_COUNTER once to skip more than one transaction.

Guess you like

Origin www.cnblogs.com/june777/p/12315272.html