[MDEV-21870] Deprecate and ignore innodb_scrub_log and innodb_scrub_log_speed Created: 2020-03-04  Updated: 2022-02-23  Resolved: 2020-03-04

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.5.2

Type: Task Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: recovery

Issue Links:
Blocks
blocks MDEV-14425 Change the InnoDB redo log format to ... Closed
blocks MDEV-18370 InnoDB: Failing assertion: lsn % OS_F... Closed
Relates
relates to MDEV-13019 scrub log cause high system load Closed
relates to MDEV-18370 InnoDB: Failing assertion: lsn % OS_F... Closed
relates to MDEV-18698 Show InnoDB's internal background thr... Open
relates to MDEV-27812 Allow innodb_log_file_size to change ... Closed

 Description   

The configuration parameter innodb_scrub_log never really worked, as reported in MDEV-13019 and MDEV-18370.

Because MDEV-14425 is changing the redo log format, the innodb_scrub_log feature would have to be adjusted for it. Due to the known problems, it is easier to remove the feature for now, and to ignore and deprecate the parameters.

If old log contents should be kept secret, then enabling innodb_encrypt_log or setting a smaller innodb_log_file_size could help.
Generated at Thu Feb 08 09:10:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.