Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4(EOL), 10.5, 10.6, 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11
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.
Attachments
Issue Links
- relates to
-
MDEV-29639 Seconds_Behind_Master is incorrect for Delayed, Parallel Replicas
-
- Closed
-
-
MDEV-17516 Replication lag issue using parallel replication
-
- Stalled
-
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue relates to MDEV-17516 [ MDEV-17516 ] |
Link |
This issue relates to |
Labels | Seconds_Behind_Master |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Fix Version/s | 10.6 [ 24028 ] | |
Fix Version/s | 10.10 [ 27530 ] | |
Fix Version/s | 10.11 [ 27614 ] |
Fix Version/s | 10.10 [ 27530 ] |
Fix Version/s | 10.4 [ 22408 ] |