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

Crashing on a corrupted page is unhelpful

    Details

      Description

      InnoDB is notoriously aborting the whole MariaDB server if it is trying to access a corrupted page.
      MDEV-12253 alleviated the issue somewhat, but not for background processing, such as the purge of no-longer-needed history.
      This bug exists in all InnoDB and XtraDB versions.
      MariaDB essentially must fix MySQL Bug#10132 Crashing the server on corrupt InnoDB page is unhelpful that was filed on April 25, 2005.

      In 10.3 with MDEV-12288 and MDEV-13536, the InnoDB purge threads will access pages more often, causing all sorts of debug assertion failures in the B-tree code. To work around this problem, tests that intentionally cause B-tree pages to be unreadable are amended with the following parameters, so that everything will be purged before the server is restarted to deal with the corruption:

      --innodb-purge-rseg-truncate-frequency=1
      --skip-innodb-fast-shutdown
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vlad.lesin Vladislav Lesin
                Reporter:
                marko Marko Mäkelä
              • Votes:
                3 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated: