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

Allow --innodb-read-only startup even when change buffer or redo logs are not empty

    XMLWordPrintable

Details

    Description

      InnoDB refuses read-only startup when the redo log or the change buffer are not empty, issuing the following kind of messages:

      [Warning] InnoDB: innodb_read_only prevents crash recovery
      		 
      [ERROR] InnoDB: Change buffer must be empty when --innodb-read-only is set!

      We should remove this arbitrary restriction in MariaDB Server.
      It would be entirely possible to apply such changes in the buffer pool, only disabling the writes back to the data files in --innodb-read-only mode.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12700 Allow innodb_read_only startup without prior slow shutdown

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13485 MTR tests fail massively with --innodb-sync-debug

          • Major - Major loss of function.
          • Closed

          Activity

            People

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