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

Backup may copy unnecessarily much log

    XMLWordPrintable

Details

    Description

      In mariadb-backup --backup there are multiple mechanisms for ensuring that a sufficient amount of the InnoDB write-ahead log (ib_logfile0) is being copied at the end of the backup.

      There is a function backup_wait_for_lsn(), which will wait for the log_copying_thread() to copy a necessary amount. But, we fail to pass the target LSN to log_copying_thread() itself.

      The log copying and recovery logic was rewritten in MDEV-14425 and some locking in backup was rewritten in MDEV-32932. Therefore, it is not trivial to apply this fix to earlier versions.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34871 BACKUP STAGE BLOCK_COMMIT had better return an InnoDB LSN

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-14425 Change the InnoDB redo log format to reduce write amplification

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

          New Feature - A new feature of the product, which has yet to be developed. MDEV-32932 port backup features from MariaDB Enterprise

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

          Activity

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              2 Vote for this issue
              Watchers:
              11 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.