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

Concurrent DDL can break xtrabackup-v2 SST in 10.2

Details

    Description

      Concurrent DDL can cause xtrabackup to see the following error in MariaDB 10.2:

      [FATAL] InnoDB: An optimized(without redo logging) DDLoperation has been performed. All modified pages may not have been flushed to the disk yet.
      

      This problem is described here:

      https://www.percona.com/blog/2017/08/08/avoiding-the-an-optimized-without-redo-logging-ddloperation-has-been-performed-error-with-percona-xtrabackup/

      This also seems to effect xtrabackup-v2 SSTs. Should the SST script use the --lock-ddl-per-table option in 10.2 to avoid this?

      Attachments

        Issue Links

          Activity

            GeoffMontee Geoff Montee (Inactive) created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            Assignee Andrii Nikitin [ anikitin ]
            anikitin Andrii Nikitin (Inactive) made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            GeoffMontee Geoff Montee (Inactive) made changes -
            Description Concurrent DDL can cause xtrabackup to see the following error in MariaDB 10.2:

            {noformat}
            [FATAL] InnoDB: An optimized(without redo logging) DDLoperation has been performed. All modified pages may not have been flushed to the disk yet.
            {noformat}

            This problem is described here:

            https://www.percona.com/blog/2017/08/08/avoiding-the-an-optimized-without-redo-logging-ddloperation-has-been-performed-error-with-percona-xtrabackup/

            This also seems to effect xtrabackup-v2 SSTs. Should the SST script use the --lock-ddl option in 10.2 to avoid this?
            Concurrent DDL can cause xtrabackup to see the following error in MariaDB 10.2:

            {noformat}
            [FATAL] InnoDB: An optimized(without redo logging) DDLoperation has been performed. All modified pages may not have been flushed to the disk yet.
            {noformat}

            This problem is described here:

            https://www.percona.com/blog/2017/08/08/avoiding-the-an-optimized-without-redo-logging-ddloperation-has-been-performed-error-with-percona-xtrabackup/

            This also seems to effect xtrabackup-v2 SSTs. Should the SST script use the --lock-ddl-per-table option in 10.2 to avoid this?
            anikitin Andrii Nikitin (Inactive) made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            Fix Version/s N/A [ 14700 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Won't Do [ 10201 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 83087 ] MariaDB v4 [ 153007 ]
            mariadb-jira-automation Jira Automation (IT) made changes -
            Zendesk Related Tickets 113927

            People

              anikitin Andrii Nikitin (Inactive)
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 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.