Using relay logs to speed up the process of point in time recovery I run into an error.
I’m testing this method to recover binlogs.
https://lefred.be/content/howto-make-mysql-point-in-time-recovery-faster/
But for each relay binlog being recovered I get one error.
ERROR] [MY-010411] [Repl] Transaction’s sequence number is inconsistent with that of a preceding one: sequence_number (1) <= previous sequence_number (1929667)
The previous sequence number is different each time but the preceding sequence of (1) is always the same.
I thought it might be that slave_preserve_commit_order was not enabled, but even with it enabled I still encounter that error.
Note: binlog_order_commits set is not set to ON for the Master if that also needs to be set to prevent this issue?
How do I tell what sequence number in the binlog is causing the issue given the replica and master status info below to calculate the offset? Also why is there a sequence number error?
Here is information from replica status and master status.
Master_Log_File: bin-log.006410
Read_Master_Log_Pos: 708184140
Relay_Log_File: bin-log.000002
Relay_Log_Pos: 1073742162
Exec_Master_Log_Pos: 1073742162
Master status
File: bin-log.006410
Position: 708184140
The start of the master binlog has this position info.
at 4
#240326 10:46:13 server id 12345678 end_log_pos 126 CRC32 0x7e689634 Start: binlog v 4, server v 8.0.32-24 created 240326 10:46:13 at startup
Warning: this binlog is either in use or was not closed properly.
ROLLBACK/!/;
at 126
The end has this info.
at 708184051
#240323 21:34:38 server id 12345678 end_log_pos 708184140 CRC32 0x72090bb8 Query thread_id=2369892 exec_time=221900 error_code=0
SET TIMESTAMP=1711254878/!/;
COMMIT
Thanks for the help.