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

    • Type: Bug
    • Status: In Progress (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 10.2, 10.3, 10.4, 10.5
    • Fix Version/s: 10.2, 10.3, 10.4, 10.5
    • Component/s: Backup
    • Labels:
      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

            Activity

              People

              Assignee:
              vlad.lesin Vladislav Lesin
              Reporter:
              vlad.lesin Vladislav Lesin
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated: