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

mariabackup --apply-log-only does generate redo log by performing rollback and possibly other tasks

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1.23, 10.1.26, 10.1(EOL)
    • 10.1.27
    • Backup
    • None

    Description

      Attached tests (from mariabackup suite) do show that mariabackup 10.1 does rollback of uncommitted transactions despite flag --apply-log-only :

      FOUND /Rollback of trx with id / in current_test 
      # expect NOT FOUND

      10.2 as well as xtrabackup 2.3.9 is not affected: 

      NOT FOUND /Rollback of trx with id / in current_test 
      # expect NOT FOUND

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14333 Mariabackup --apply-log-only crashes if incomplete transactions with update_undo logs are present

          • Major - Major loss of function.
          • Closed
          is caused by

          Task - A task that needs to be done. MDEV-9566 Add xtrabackup tool to MariaDB 10.1

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13890 mariabackup.xb_compressed_encrypted failed in buildbot, InnoDB: assertion failure

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13822 Mariabackup --prepare --incremental sets file size incorrectly

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13797 InnoDB may hang if shutdown is initiated soon after startup, while rolling back recovered incomplete transactions

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            anikitin Andrii Nikitin (Inactive) created issue -
            anikitin Andrii Nikitin (Inactive) made changes -
            Field Original Value New Value
            anikitin Andrii Nikitin (Inactive) made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            marko Marko Mäkelä made changes -
            Summary --apply-log-only does perform rollback mariabackup --apply-log-only does generate redo log by performing rollback and possibly other tasks
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Assignee Marko Mäkelä [ marko ] Vladislav Vaintroub [ wlad ]
            marko Marko Mäkelä made changes -
            Assignee Vladislav Vaintroub [ wlad ] Marko Mäkelä [ marko ]
            marko Marko Mäkelä made changes -
            Status Confirmed [ 10101 ] In Progress [ 3 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Fix Version/s 10.1.27 [ 22609 ]
            Fix Version/s 10.1 [ 16100 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            anikitin Andrii Nikitin (Inactive) made changes -
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 82584 ] MariaDB v4 [ 152824 ]
            mariadb-jira-automation Jira Automation (IT) made changes -
            Zendesk Related Tickets 137456

            People

              marko Marko Mäkelä
              anikitin Andrii Nikitin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.