You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening Support Data Collector there should be no error about innodb_log_file_size when the variable innodb_redo_log_capacity is set, which supercedes the innodb_log_files_in_group and innodb_log_file_size variables.
Actual behavior
An error is shown:
The setting innodb_log_file_size must be at least 256 MB.
I believe innodb_log_file_size variable is also checked when doing a clean install.
However, it has been a while since I performed a clean install, so I am not certain.
Screenshots
The text was updated successfully, but these errors were encountered:
arndkeyz
changed the title
Bug - [short text describing the problem]
innodb_log_file_size error while using innodb_redo_log_capacity
Feb 17, 2025
arndkeyz
changed the title
innodb_log_file_size error while using innodb_redo_log_capacity
Bug - innodb_log_file_size error while using innodb_redo_log_capacity
Feb 17, 2025
Environment
Expected behavior
When opening Support Data Collector there should be no error about innodb_log_file_size when the variable innodb_redo_log_capacity is set, which supercedes the innodb_log_files_in_group and innodb_log_file_size variables.
Actual behavior
An error is shown:
The setting innodb_log_file_size must be at least 256 MB.
How to reproduce
Steps to reproduce the behavior:
Additional information
https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log.html#innodb-modifying-redo-log-capacity
https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_redo_log_capacity
This new parameter was introduced with MySQL 8.0.30. There was no issue prior to that version.
I believe innodb_log_file_size variable is also checked when doing a clean install.
However, it has been a while since I performed a clean install, so I am not certain.
Screenshots
The text was updated successfully, but these errors were encountered: