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

mariabackup failed after upgrade 10.11.10

Details

    Description

      Hi Team,

      We upgraded from 10.11.8 to 10.11.10 two weeks ago and since then mariabackup keeps failing with the following logs.

      [00] 2025-02-24 00:41:42 Waiting for log copy thread to read lsn 160568393706001
      		 
      [00] 2025-02-24 00:41:43 Retrying read of log at LSN=160515356496404
      		 
      [00] 2025-02-24 00:41:44 Retrying read of log at LSN=160515356496404
      		 
      [00] 2025-02-24 00:41:45 Retrying read of log at LSN=160515356496404
      		 
      [00] 2025-02-24 00:41:46 Retrying read of log at LSN=160515356496404
      		 
      [00] 2025-02-24 00:41:47 Retrying read of log at LSN=160515356496404
      		 
      [00] 2025-02-24 00:41:47 Was only able to copy log from 160487092534834 to 160515356496404, not 160568393706001; try increasing innodb_log_file_size
      		 
      mariabackup: Stopping log copying thread.

      I judged that this was caused by a small innodb_log_file_size value, so I tested to change it to an appropriate value and got the following results.

      • MariaDB engine ver : 10.11.10 / mariabackup engine ver : 10.11.10
        innodb_log_file_size = 1G - failed
        innodb_log_file_size = 4G - failed
        innodb_log_file_size = 8G - failed
      • MariaDB engine ver : 10.11.8 / mariabackup engine ver : 10.11.8
        innodb_log_file_size = 1G - success
        innodb_log_file_size = 4G - success
      • MariaDB engine ver : 10.11.10 / mariabackup engine ver : 10.11.8
        innodb_log_file_size = 1G - success

      Is this a new bug different from MDEV-34062?
      I would like to know if there is any impact on the acceptability of backups from engine 10.11.10 to mariabackup 10.11.8 in production environments.

      Thanks and Regard.

      Attachments

        1. 2025-02-22_pnucedbm02_backup_failed.log
          5.87 MB
          baek seung ho
        2. 2025-03-01_pnucedbm02_backup_success.log
          1.26 MB
          baek seung ho
        3. backup_failed.log
          631 kB
          baek seung ho
        4. backup_success.log
          409 kB
          baek seung ho
        5. innodb_parameter.txt
          25 kB
          baek seung ho
        6. MDEV_36159.txt
          1 kB
          Axel Schwenke

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-14992 BACKUP: in-server backup

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30000 make mariadb-backup to force an innodb checkpoint

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34062 mariadb-backup --backup is extremely slow at copying ib_logfile0

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34070 mariadb-backup --prepare with larger --use-memory may be slower

          • Major - Major loss of function.
          • Confirmed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35791 mariadb-backup 10.11.10 failed to create backup

          • Major - Major loss of function.
          • Needs Feedback

          New Feature - A new feature of the product, which has yet to be developed. MDEV-14992 BACKUP: in-server backup

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

          New Feature - A new feature of the product, which has yet to be developed. MDEV-21105 Port clone plugin API (MYSQL_CLONE_PLUGIN) from MySQL

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21923 LSN allocation is a bottleneck

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

          Activity

            People

              debarun Debarun Banerjee
              supbaek baek seung ho
              Votes:
              4 Vote for this issue
              Watchers:
              15 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.