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

refactor XA binlogging for better integration with BGC/replication/recovery

    XMLWordPrintable

Details

    • Task
    • Status: In Progress (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 11.9
    • Replication, XA
    • None

    Description

      The task is to improve on MDEV-742 design of the XA binlogging.
      When binlog is ON, execute XA-{prepare, commit, rollback} via
      MYSQL_BIN_LOG::run_ordered_commit, so that at the end of binlog_{prepare, commit, rollback} the operation over the xa transaction is completed as far as (parallel) replication/recovery is concerned. Specifically its XID is available for next use, incl for
      xa-complete by another slave parallel commit/rollback or xa-start of a new same xid transaction.

      Attachments

        1. bug1.txt
          4 kB
        2. bug10.txt
          6 kB
        3. bug2.txt
          3 kB
        4. bug3.txt
          3 kB
        5. bug4.txt
          0.5 kB
        6. bug5.txt
          7 kB
        7. bug6.txt
          5 kB
        8. bug7.txt
          7 kB
        9. bug8.txt
          6 kB
        10. bug9.txt
          5 kB

        Issue Links

          blocks

          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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32896 Unstable XA + binglog tests, with possible MDEV-32830 caused issues

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32852 Assertion `is_prepared_xa(thd) || ((thd->lex->sql_command == SQLCOM_XA_ROLLBACK && thd->transaction->xid_state.get_state_code() == XA_IDLE) || thd->lex->xa_opt == XA_ONE_PHASE)' failed in TC_LOG::run_commit_ordered

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32857 Assertion `thd->lex->sql_command == SQLCOM_XA_COMMIT || thd->lex->sql_command == SQLCOM_XA_ROLLBACK' failed in TC_LOG::run_commit_ordered

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32852 Assertion `is_prepared_xa(thd) || ((thd->lex->sql_command == SQLCOM_XA_ROLLBACK && thd->transaction->xid_state.get_state_code() == XA_IDLE) || thd->lex->xa_opt == XA_ONE_PHASE)' failed in TC_LOG::run_commit_ordered

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32857 Assertion `thd->lex->sql_command == SQLCOM_XA_COMMIT || thd->lex->sql_command == SQLCOM_XA_ROLLBACK' failed in TC_LOG::run_commit_ordered

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

          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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32020 XA transaction replicates incorrectly, must be applied at XA COMMIT, not XA PREPARE

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

          Activity

            People

              Elkin Andrei Elkin
              Elkin Andrei Elkin
              Votes:
              1 Vote for this issue
              Watchers:
              9 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.