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

Document what rollback-xa mariabackup option does

Details

    Description

      https://mariadb.com/kb/en/mariabackup-options/#-rollback-xa has removed the warning to no longer use this option (from fixed releases), but doesn't explain what the option does

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-742 LP:803649 - Xa recovery failed on client disconnection

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21168 Active XA transactions stop slave from working after backup was restored.

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22398 mariabackup.innodb_xa_rollback fails on repeat

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            GeoffMontee Geoff Montee (Inactive) added a comment - - edited

            Hi vlad.lesin,

            Is this a good description?:

            By default, Mariabackup will not commit or rollback uncommitted XA transactions, and when the backup is restored, any uncommitted XA transactions must be manually committed using XA COMMIT or manually rolled back using XA ROLLBACK.

            In MariaDB 10.2, MariaDB 10.3, and MariaDB 10.4, Mariabackup's --rollback-xa option can be used to rollback uncommitted XA transactions while performing a --prepare operation, so that they do not need to be manually committed or rolled back when the backup is restored.

            This option is not present in MariaDB 10.5, because the server has more robust ways of handling uncommitted XA transactions in that version.

            Please feel free to reassign this back to me when you provide feedback, and I will make the documentation change.

            Thanks!

            GeoffMontee Geoff Montee (Inactive) added a comment - - edited Hi vlad.lesin , Is this a good description?: By default, Mariabackup will not commit or rollback uncommitted XA transactions, and when the backup is restored, any uncommitted XA transactions must be manually committed using XA COMMIT or manually rolled back using XA ROLLBACK. In MariaDB 10.2, MariaDB 10.3, and MariaDB 10.4, Mariabackup's --rollback-xa option can be used to rollback uncommitted XA transactions while performing a --prepare operation, so that they do not need to be manually committed or rolled back when the backup is restored. This option is not present in MariaDB 10.5, because the server has more robust ways of handling uncommitted XA transactions in that version. Please feel free to reassign this back to me when you provide feedback, and I will make the documentation change. Thanks!
            vlad.lesin Vladislav Lesin added a comment -

            GeoffMontee, yes, this is correct explanation.

            vlad.lesin Vladislav Lesin added a comment - GeoffMontee , yes, this is correct explanation.

            People

              GeoffMontee Geoff Montee (Inactive)
              greenman Ian Gilfillan
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.