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

Async rollback prepared transactions during binlog crash recovery

Details

    Description

      When doing server recovery, the active transactions will be rolled
      back by InnoDB background rollback thread automatically. The
      prepared transactions will be committed or rolled back accordingly
      by binlog recovery. Binlog recovery is done in main thread before
      the server can provide service to users. If there is a big
      transaction to rollback, the server will not available for a long
      time.

      It is better to make the prepared transactions to be rolled back by the background rollback thread.

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Andrei Elkin made transition -
            Open In Progress
            15d 5h 53m 1
            Andrei Elkin made transition -
            In Progress In Review
            15s 1
            Andrei Elkin made transition -
            In Review Stalled
            1m 8s 1
            Marko Mäkelä made transition -
            Stalled In Review
            54d 15h 57m 1
            Kristian Nielsen made transition -
            In Review In Testing
            40d 3h 22m 1
            Matthias Leich made transition -
            In Testing Stalled
            9d 1h 39m 1
            Marko Mäkelä made transition -
            Stalled In Testing
            5m 26s 1
            Marko Mäkelä made transition -
            In Testing Closed
            31d 8h 4m 1

            People

              marko Marko Mäkelä
              libing Libing Song
              Votes:
              0 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.