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

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

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

          Activity

            Transition Time In Source Status Execution Times
            Vladislav Lesin made transition -
            Open In Progress
            7d 4h 41m 1
            Vladislav Lesin made transition -
            In Progress Stalled
            15s 1
            Vladislav Lesin made transition -
            Stalled In Progress
            108d 10h 36m 1
            Vladislav Lesin made transition -
            In Progress Closed
            15d 13h 57m 1

            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.