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

InnoDB recovery and mariadb-backup --prepare fail to report detailed progress

Details

    Description

      A user is facing this scenario where mariabackup --prepare has been running for 12+ hours, and it's reporting page numbers to recover. Then it goes on to multiple iterations of recovery with no indication of how much work is remaining or how much time remains to complete the process.

      It will be great if `--prepare` can report the percentage of pages recovery completed per iteration and a global percentage completion consolidating all iteration batches.

      Attachments

        1. preparelog.txt
          332 kB
          Faisal Saeed
        2. big_restore.log
          33 kB
          Timofey Turenko

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Marko Mäkelä made transition -
            Open Needs Feedback
            1d 3h 26m 2
            Marko Mäkelä made transition -
            Needs Feedback Open
            35d 12h 56m 2
            Marko Mäkelä made transition -
            Open Confirmed
            1m 40s 1
            Marko Mäkelä made transition -
            Confirmed In Progress
            114d 22h 9m 1
            Marko Mäkelä made transition -
            In Progress In Testing
            25d 22h 42m 1
            Matthias Leich made transition -
            In Testing Stalled
            21d 3h 40m 1
            Marko Mäkelä made transition -
            Stalled Closed
            3d 2h 34m 1

            People

              marko Marko Mäkelä
              Faisal Faisal Saeed (Inactive)
              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.