mysql> show slave status\G ....... Relay_Log_File: localhost-relay-bin.000535 Relay_Log_Pos: 21795072 Relay_Master_Log_File: localhost-bin.000094 Slave_IO_Running: Yes Slave_SQL_Running: No Replicate_Do_DB: Replicate_Ignore_DB: ......
A solution,
Slave_SQL_Running: No
1. program may be a write operation on the slave
2. After the slave machine may be restarted, transaction rollback caused.
Is usually caused by transaction rollback:
Solution:
mysql> stop slave ; mysql> set GLOBAL SQL_SLAVE_SKIP_COUNTER=1; mysql> start slave ;
Solution II (recommended)
First, the service stopped Slave: slave stop
to the primary server host status view:
Record File Position and the corresponding value
Into the master
mysql> show master status; +----------------------+----------+--------------+------------------+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +----------------------+----------+--------------+------------------+ | localhost-bin.000094 | 33622483 | | | +----------------------+----------+--------------+------------------+ 1 row in set (0.00 sec)
Then the slave server to perform a manual synchronization:
mysql> change master to > master_host='master_ip', > master_user='user', > master_password='pwd', > master_port=3306, > master_log_file=localhost-bin.000094', > master_log_pos=33622483 ; 1 row in set (0.00 sec) mysql> start slave ; 1 row in set (0.00 sec)
start slave
mysql> show slave status Master_Log_File: localhost-bin.000094 Read_Master_Log_Pos: 33768775 Relay_Log_File: localhost-relay-bin.000537 Relay_Log_Pos: 1094034 Relay_Master_Log_File: localhost-bin.000094 Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_Do_DB:
CHANGE MASTER TO master_host = '192.168.0.61',
master_port = 3306,
master_user = 'root',
master_password = 'root',
master_log_file = 'mysql-bin.000014',
master_log_pos = 489;