Slave SQL: Relay log read failure: Could not parse relay log event entry.

3075 ワード

正午に警報を監視して、あるは機abから複製して中断して、上陸します

show slave status\G

に見える

Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.

sqlスレッドはrelay-logを読み取ることができず、relay-logの破損を推定します!
slaveを再起動してみます

stop slave;
start slave;

ステータスの表示はこのエラーのままです.
エラー・ログの表示

140220 22:26:49 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000173' at position 939494307, relay log '/var/www/logs/mysql/mysql-relay-bin.000535' position: 359274967
140220 22:26:49 [ERROR] Error in Log_event::read_log_event(): 'Event too small', data_len: 0, event_type: 0
140220 22:26:49 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
140220 22:26:49 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 1594
140220 22:26:49 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000173' position 939494307
140220 22:26:49 [Note] Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysql-bin.000174' at position 623712958

主従レプリケーションのsqlスレッドが間違っていることを意味し、salveレプリケーションプロセスを再起動することをお勧めします.
レプリケーションioスレッドからプライマリ

Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysql-bin.000174' at position 623712958

sqlスレッドでエラーが発生したため、この情報を無視して、sqlスレッドの位置に重点を置くことができます.

slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000173' position 939494307

レプリケーションプロセスを複数回再起動しようとしてもこの問題は解決できないため、masterを再変更しようとします.(fileとpositionは上のエラーログの情報を使用します)

stop slave;
 change master to master_log_file='mysql-bin.000173',master_log_pos=939494307;
start slave;

再度slave状態を確認して、すでに正常です!

mysql実装Oracleのrow_number over partition by

docker mysqlタイムゾーンが間違っています