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

innodb_undo_log_truncate is not crash-safe

Details

    Description

      Likely caused by MDEV-18976, innodb_undo_log_truncate=ON lost its crash-safety status. The reason is that the pages of the being-truncated undo log tablespace were not marked as modified by the mini-transaction. The logic of logging page-free operations was changed in MDEV-18976.

      The failures are rare and hard to repeat, but there is some indication that a small fix to trx_purge_free_segment() would fix this.

      I did not find any matching failures of the test innodb.undo_log_truncate between 10.3 and 10.5.

      Attachments

        Issue Links

          Activity

            marko Marko Mäkelä created issue -
            marko Marko Mäkelä made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            issue.field.resolutiondate 2022-06-14 13:09:28.0 2022-06-14 13:09:28.149
            marko Marko Mäkelä made changes -
            Fix Version/s 10.6.9 [ 27507 ]
            Fix Version/s 10.7.5 [ 27505 ]
            Fix Version/s 10.8.4 [ 27503 ]
            Fix Version/s 10.9.2 [ 27115 ]
            Fix Version/s 10.6 [ 24028 ]
            Fix Version/s 10.7 [ 24805 ]
            Fix Version/s 10.8 [ 26121 ]
            Fix Version/s 10.9 [ 26905 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              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.