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

Some DDLs like ANALYZE can complete on parallel slave out of order

    XMLWordPrintable

Details

    Description

      ANALYZE TABLE can complete on slave before a preceding transaction does so. E.g in case
      of the binlogging slave and the strict gtid mode something like the following error

      Last_SQL_Error: An attempt was made to binlog GTID 812700-812700-487719 which would create an out-of-order sequence number with existing GTID 812700-812700-487721, and gtid strict mode is enabled
      

      may occur. In the specific paste above GTID 812700-812700-487721 corresponds to ANALYZE, and GTID 812700-812700-487719 to a regular BEGIN..COMMIT transaction binlogged earlier.
      The error indicates the transaction binlogging on slave violates the master binlog order.

      The reason of the failure has been identified as a flaw introduced by MDEV-17515.

      Attachments

        Activity

          People

            Elkin Andrei Elkin
            Elkin Andrei Elkin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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