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

Capture corrupted binlog events

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • N/A
    • Replication
    • None

    Description

      This toplevel ticket captures work related to binlog corruption. Broadly speaking, there appear to be four paths forward, three on the server and one in the client. On the server, we could (1) implement sandboxing for plugins (Andrei's comment "prevent faulty plugins"), (2) prevent binlog corruption from occurring, (3) warn when binlog corruption occurs (e.g. by detecting possible binlog corruption with timestamp checks as described in the ticket). On the client, we can find traces of corruption (some minimum length string of null bytes) enabled a new commandline option.

      Attachments

        Issue Links

          includes

          Task - A task that needs to be done. MDEV-34685 Sandbox plugins away from replication mechanics

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-34686 Prevent binlog corruptions

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-34687 Warn when binlog corruption occurs

          • Major - Major loss of function.
          • In Review

          Task - A task that needs to be done. MDEV-34688 Client-side binlog corruption detection

          • Major - Major loss of function.
          • Open

          Activity

            People

              Gosselin Dave Gosselin
              Elkin Andrei Elkin
              Votes:
              1 Vote for this issue
              Watchers:
              8 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.