Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-39051

Optimistic Relay Log Crash Recovery for non-GTID replication

    XMLWordPrintable

Details

    Description

      MDEV-38907 “Relay Log auto-recovery” can be extended to non-GTID replication.

      The challenge is, unlike GTID, which increments every event group (e.g., transaction), file-position increments every event.
      This means the non-GTID mode must either

      • truncate only the trailing corrupted event, not a whole group
        • A downside is that this will become yet another difference from GTID replication.
      • additionally rewind the file-position when truncating an entire group
        • If (needs review) the @@master_info_file saving between events is safe, then because the binary log does not rotate in the middle of a group, @@master_info_file is reliable for reloading master_log_file, and only master_log_pos needs "recovery".
          The worst case would be a master-side ROTATE_EVENT being the corrupted event, but it's okay to resume from the very end of the previous binary log.

      Attachments

        Issue Links

          is part of

          Task - A task that needs to be done. MDEV-8946 Add replication crash-safety for non-GTID slave.

          • Major - Major loss of function.
          • Open
          relates to

          Technical task - A technical task. MDEV-37046 How does non-GTID replication implement this with crash compatibility?

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-37584 Optimize relay_log.info Flush

          • Major - Major loss of function.
          • Open

          Technical task - A technical task. MDEV-38909 GTID State for Relay Log

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          split from

          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 Review

          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.