Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-38908 Header GTID Lists in Relay Logs
  3. MDEV-38909

GTID State for Relay Log

    XMLWordPrintable

Details

    • Technical task
    • Status: Open (View Workflow)
    • Critical
    • Resolution: Unresolved
    • None
    • 13.0
    • Replication
    • None
    • Q1/2026 Server Development

    Description

      Given that GTID Lists should record states, not positions, Relay Logs will also need to track states, not just Gtid_IO_Pos.
      Gtid_IO_Pos would then be derived from this "Gtid_IO_State".

      Since Relay Logs will track states like in Binary Logs, these two classes can share code, including the recovery procedure that reloads the state.
      For Relay Logs, if this reload procedure fails, they shall fall back to @@relay_log_recovery - or better, MDEV-38907.

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-38907 Optimistic Relay Log Crash Recovery

          • Critical - Crashes, loss of data, severe memory leak.
          • In Progress
          split to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-38912 GTID .state and Index for Relay Log

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

              ParadoxV5 Jimmy Hú
              ParadoxV5 Jimmy Hú
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.