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

Redefine the innodb_encrypt_log format

    XMLWordPrintable

Details

    • 10.2.4-1, 10.2.4-2

    Description

      WL#8845 introduced a redo log format identifier in MySQL 5.7.9.

      The MariaDB extension innodb_encrypt_log should distinguish encrypted redo logs from cleartext ones by the redo log format tag. In this way, an attempt to start up MySQL 5.7 after a crash of MariaDB with innodb_encrypt_log=1 will result in a clear error message rather than some strange-looking crash.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-12041 Implement key rotation for innodb_encrypt_log

          • Major - Major loss of function.
          • Closed
          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13061 innodb_encrypt_log recovery is spamming the error log

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13834 10.2 wrongly recognizes 10.1.10 innodb_encrypt_log=ON data as after-crash and refuses to start

          • Major - Major loss of function.
          • Closed
          includes

          Task - A task that needs to be done. MDEV-12061 Allow innodb_log_files_in_group=1

          • Major - Major loss of function.
          • Closed
          is part of

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11873 Unnecessary InnoDB warnings upon bootstrap

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12103 Reduce the time of looking for MLOG_CHECKPOINT during crash recovery

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14874 innodb_encrypt_log corrupts the log when the LSN crosses 32-bit boundary

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-9011 Redo log encryption does not work

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-11432 Change the informational redo log format tag to say "MariaDB 10.2.3"

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13253 After rebuilding redo logs, InnoDB can leak data from redo log buffer

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13318 Crash recovery failure after the server is killed during innodb_encrypt_log startup

          • Major - Major loss of function.
          • Closed

          Activity

            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.