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

Backup may copy unnecessarily much log

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

          Activity

            Transition Time In Source Status Execution Times
            Marko Mäkelä made transition -
            Open In Progress
            4m 42s 1
            Marko Mäkelä made transition -
            Stalled In Progress
            7h 12m 1
            Marko Mäkelä made transition -
            In Progress In Review
            1d 20h 51m 2
            Marko Mäkelä made transition -
            Stalled In Review
            14d 21h 38m 1
            Debarun Banerjee made transition -
            In Review Stalled
            51d 23h 26m 3
            Marko Mäkelä made transition -
            Stalled In Testing
            1m 55s 1
            Matthias Leich made transition -
            In Testing Stalled
            4d 5h 56m 1
            Marko Mäkelä made transition -
            Stalled Closed
            54m 4s 1

            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.