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

Implement crash-safe logging of the user XA

    XMLWordPrintable

Details

    • Bug
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5
    • 10.6
    • Replication

    Description

      This task is ensued by MDEV-742 and implements the upstream's Bug#76233

      In fact there's no issue in the ordering of logging of XA PREPARE into the binary log and transaction preparing in Engine. The chosen by upstream method of the logging goes first is not really incorrect but just needs
      some refinement of the server recovery.

      So in case the server crashes having XA-prepared "transaction" binlogged but not yet
      prepared in Engine, its next recovery must be augmented with identifying the XA-prepared's events in the binlog and resubmitting the transaction for preparing in Engine.

      XA-COMMIT or XA-ROLLBACK are logged compatibly with XA-PREPARE and therefore
      a similar issue arises when the server crashes after binary logging but before actual transaction completion in Engine. The same technique must be used to identify and resubmit to commit-or-rollback.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34526 Mariadb crashed and replication got broken after MariaDB services came up

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26652 xa transactions binlogged in wrong order

          • Major - Major loss of function.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29642 Server Crash During XA Prepare Can Break Replication

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31921 Replication Breaks after Recovering a Prepared-but-not-binlogged XA ONE PHASE Transaction

          • Major - Major loss of function.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. MDEV-31949 slow parallel replication of user xa

          • Major - Major loss of function.
          • Stalled

          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

          New Feature - A new feature of the product, which has yet to be developed. MDEV-18959 Engine transaction recovery through persistent binlog

          • Major - Major loss of function.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31998 XA PREPARE should do binlog_prepare last

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

          Task - A task that needs to be done. MDEV-21777 Implement crash-safe execution the user XA on binlog-less slave

          • Major - Major loss of function.
          • Open
          links to

          Web Link Bug #76233 XA prepare is logged ahead of engine prepare

          Activity

            People

              bnestere Brandon Nesterenko
              Elkin Andrei Elkin
              Votes:
              2 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.