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

Active XA transactions stop slave from working after backup was restored.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
    • 10.2.32, 10.3.23, 10.4.13
    • Backup
    • None

    Description

      When using Mariabackup to create a slave, the slave had XA transactions active which stopped the slave from working.

      The easiest way to fix this is that when mariabackup runs recover on the backup, set up --tc-heuristic-recover=ROLLBACK.

      This will ensure that any XA prepared transaction are rolled back on the slave.
      This is the correct thing to do as the gtid position that is copied as part of mariabackup doesn't have any part of the XA transactions and when starting the slave against the master, the XA transaction will be copied to the slave.

      Attachments

        Issue Links

          is blocked by

          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
          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

          Task - A task that needs to be done. MDEV-21980 Remove overloaded references to "XA transactions" in log messages

          • Major - Major loss of function.
          • Open

          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

          Task - A task that needs to be done. MDEV-21117 refine the server binlog-based recovery for semisync

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

          Task - A task that needs to be done. MDEV-22614 "mariabackup --prepare" exits with code 0 even though innodb error is logged

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-22656 Document what rollback-xa mariabackup option does

          • Major - Major loss of function.
          • Closed
          split to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30794 port --rollback-xa of MDEV-21168 fixes to 10.5+

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

          Activity

            People

              vlad.lesin Vladislav Lesin
              vlad.lesin Vladislav Lesin
              Votes:
              1 Vote for this issue
              Watchers:
              12 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.