[MDEV-31745] First Event After Starting a Delayed Parallel Replica Shows 0 Seconds_Behind_Master Created: 2023-07-19  Updated: 2023-11-28

Status: Open
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.4, 10.5, 10.6, 10.8, 10.9, 10.10, 10.11
Fix Version/s: 10.4, 10.5, 10.6, 10.11

Type: Bug Priority: Major
Reporter: Brandon Nesterenko Assignee: Brandon Nesterenko
Resolution: Unresolved Votes: 0
Labels: Seconds_Behind_Master

Issue Links:
Relates
relates to MDEV-29639 Seconds_Behind_Master is incorrect fo... Closed
relates to MDEV-17516 Replication lag issue using parallel ... Stalled

 Description   

A parallel replica delays all events that the SQL Thread reads in. With the changes from MDEV-29639, a replica will update Seconds_Behind_Master on the first user-generated event after idling. This mismatch leads to a parallel replica displaying 0 for Seconds_Behind_Master for the entire duration of a configured MASTER_DELAY if it is delaying an internal event, even if there are user-generated events that the IO thread has seen and written to the relay log. One example would be when delaying the first event after issuing START SLAVE.


Generated at Thu Feb 08 10:26:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.