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

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

    XMLWordPrintable

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

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32042 Special handling of crash recovery in buf_page_get_gen() may cause overhead

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31386 InnoDB: Failing assertion: page_type == i_s_page_type[page_type].type_value

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31827 InnoDB multi-batch recovery stops prematurely

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31080 InnoDB: Failing assertion: space->size == check.size in fil_validate() during deferred tablespace recovery

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11027 InnoDB log recovery is too noisy

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31350 test innodb.recovery_memory failed on '21 failed attempts to flush a page'

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31353 InnoDB recovery hangs after reporting corruption

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31362 recv_sys_t::apply(bool): Assertion `!last_batch || recovered_lsn == scanned_lsn' failed

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

          Task - A task that needs to be done. MDEV-14481 Execute InnoDB crash recovery in the background

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-30053 mariabackup should indicate memory needed for prepare

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32029 Assertion failures in log_sort_flush_list upon crash recovery

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

          Activity

            People

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