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

Trx abort does not work in autocommit mode

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1.16
    • 10.1.17
    • Galera, wsrep
    • None

    Description

      In Galera cluster, a local transaction could be aborted on the node if it conflicts with a remote transaction (higher priority). During code inspection, it was found that ha_abort_transaction() (function responsible for transaction abort) only looked for engines registered under standard transaction (st_transactions::all, and not statement transaction st_transactions::stmt). Thus, a node won't be able to abort a transaction executing in autocommit mode.

      Attachments

        Issue Links

          Activity

            nirbhay_c Nirbhay Choubey (Inactive) created issue -
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            Field Original Value New Value
            Assignee Nirbhay Choubey [ nirbhay_c ]
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            Summary Abort does not work in autocommit mode Trx abort does not work in autocommit mode
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            Fix Version/s 10.1.17 [ 22102 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            nirbhay_c Nirbhay Choubey (Inactive) made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 76544 ] MariaDB v4 [ 150698 ]

            People

              nirbhay_c Nirbhay Choubey (Inactive)
              nirbhay_c Nirbhay Choubey (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.