Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
11.7(EOL), 11.8
-
None
Description
Test rpl.rpl_parallel_sbm can fail with error "At line 164: Slave_last_event_time is not equal to Master_last_event_time despite being up-to-date":
rpl.rpl_parallel_sbm 'mix' w5 [ fail ]
|
Test ended at 2025-01-25 04:56:56
|
|
CURRENT_TEST: rpl.rpl_parallel_sbm
|
mysqltest: At line 164: Slave_last_event_time is not equal to Master_last_event_time despite being up-to-date
|
|
The result from queries just before the failure was:
|
< snip >
|
# catch up to the master before checking SBM.
|
connection server_2;
|
LOCK TABLES t1 WRITE;
|
include/start_slave.inc
|
connection slave;
|
# SQL delay has no impact for the rest of the test case, so ignore it
|
include/sync_with_master_sql_delay_debug_sync.inc
|
set debug_sync= "now WAIT_FOR at_sql_delay";
|
set debug_sync= "now SIGNAL continue_sql_thread";
|
# Waiting for replica to get blocked by the table lock
|
# Sleeping 1s to increment SBM
|
# Ensuring Seconds_Behind_Master increases after sleeping..
|
# ..done
|
connection server_2;
|
UNLOCK TABLES;
|
include/sync_with_master_gtid.inc
|
# MDEV-33856: New definition for Seconds_Behind_Master
|
# Ensuring Slave_last_event_time is now up-to-date once event is executed
|
# Slave_last_event_time: 1737781011 (2025-01-25 04:56:51)
|
# Master_last_event_time: 1737781013 (2025-01-25 04:56:53)
|
Note the Slave_last_event_time and Master_last_event_time are indeed different, when the slave has just before synced with the master gtid.
Attachments
Issue Links
- is caused by
-
MDEV-33856 Alternative Replication Lag Representation via Received/Executed Master Binlog Event Timestamps
-
- Closed
-
Pushed into 11.7 as 01fafd45eba