Details
-
New Feature
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
Q1/2026 Server Development
Description
Currently, GTID Lists in Relay logs mostly only come from the primary, so a Relay Log file may not have a List if the Relay Log switched on its own.
Having header GTID Lists in Relay Logs (like Binary Logs) will ensure there is at least one in the file.
GTID Lists allow a relay log file to report its position without context from Gtid_Slave_Pos and possibly previous files.
Note that GTID Lists are intended to record the exact state of a log, not merely a position, so they work with domains that are out of order by different server IDs.
Thus, GTID Lists will also bring better integration with mariadb-binlog, especially after MDEV-37231.
The SQL thread can also use these headers to seek through files without collecting every GTID in the file. (Split to MDEV-XXXXX)
Attachments
Issue Links
- blocks
-
MDEV-4698 With GTID replication, relay logs cannot be relied upon while purging binary logs on master
-
- In Progress
-
- relates to
-
MDEV-37231 mariadb-binlog GTID --start/stop-position ignoring Server ID
-
- Open
-
- split to
-
MDEV-38911 GTID List based Relay Log seeking
-
- Open
-
1.
|
GTID State for Relay Log |
|
Open | Jimmy Hú |