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

Galera Cluster mariabackup fail

    XMLWordPrintable

Details

    Description

      Our service is MariaDB Galera Cluster. (innodb_log_file_size=512M)
      We upgraded from 10.1 to 10.11. (innodb_log_file_size=4G)
      We changed innodb_log_file_size=4G while upgrading to 10.11.
      After the upgrade, mariabackup failed.
      I checked the jira contents by referring to the mariabackup log contents.
      The following is a list of bugs that I reviewed.

      MDEV-27621
      MDEV-35791
      MDEV-36159
      MDEV-36237
      MDEV-30000
      MDEV-35442

      Referred to MDEV-36237.
      This phenomenon occurred because the amount of redo writes was greater than the speed of performing mariabackup, so I increased innodb_log_file_size to 30GB.
      And I upgraded MariaDB to 10.11.13.
      And I ran mariabackup again, but it failed the same way.

      I am attaching the mariabackup log.

      Attachments

        1. mysql.err
          762 kB
          jeonwoosang
        2. BKUP_2025061823.log
          135 kB
          jeonwoosang

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-36159 mariabackup failed after upgrade 10.11.10

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-36237 mariabackup fails with 'try increasing innodb_log_file_size'

          • Major - Major loss of function.
          • Needs Feedback

          Activity

            People

              marko Marko Mäkelä
              jeonwoosang jeonwoosang
              Votes:
              6 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.