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

Allow innodb_read_only startup without prior slow shutdown

Details

    Description

      The parameter innodb_read_only which first appeared in MySQL 5.6 and MariaDB Server 10.0 disallows startup if the redo log is not logically empty or if the change buffer is not empty.

      It is technically possible to apply the needed changes in memory only, without writing them back to the data files. If MariaDB does that, it will be possible to check hot backups in a read-only fashion without any preparatory steps.

      Attachments

        Issue Links

          includes

          Task - A task that needs to be done. MDEV-19514 Defer change buffer merge until pages are requested

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

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

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13614 Allow --innodb-read-only startup even when change buffer or redo logs are not empty

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-19176 Do not run out of InnoDB buffer pool during recovery

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11814 Refuse innodb_read_only startup if crash recovery is needed

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12699 Improve crash recovery of corrupted data pages

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14080 InnoDB shutdown sometimes hangs

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15202 innodb.log_file_size failed in buildbot - Can't initiate database recovery, running in read-only-mode

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-29694 Remove the InnoDB change buffer

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

          Activity

            Transition Time In Source Status Execution Times
            Marko Mäkelä made transition -
            Open Confirmed
            		209d 50m 1
            Thirunarayanan Balathandayuthapani made transition -
            Confirmed In Progress
            		656d 2h 2m 1
            Thirunarayanan Balathandayuthapani made transition -
            In Progress Stalled
            		244d 23h 1
            Marko Mäkelä made transition -
            Stalled Closed
            		1113d 21h 16m 1

            People

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