InnoDB redo log capacity Health Check in Confluence Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
You may see the following warning in Confluence under Instance health checks in the Database section: “Your innodb_redo_log_capacity of 1GB is too small. You should increase innodb_redo_log_capacity to at least 2GB.”
The full error message is below.
Health check 'InnoDB Redo Log Capacity' failed with severity 'warning': 'Your innodb_redo_log_capacity of 1GB is too small. You should increase innodb_redo_log_capacity to at least 2GB.'
Cause
This warning appears when:
The maximum allowed packet size of the MySQL server is too small
The InnoDB redo log capacity value is less than the required size (2GB)
For more information, see the MySQL documentation:
Solution
Resolution for MySQL 8.0.30 and later:
Shut down Confluence
Shut down MySQL
Edit the
my.cnffile (my.inion Windows) on your MySQL server (More about MySQL option files)Locate the
[mysqld]section in the fileAdd or modify the following parameters:
Set
max_allowed_packetto512MSet
innodb_redo_log_capacityto at least2GBFor details, see the MySQL installation guide for Confluence
Save your changes
Start MySQL
Start Confluence
Important notes:
Set
innodb_redo_log_capacityto at least 2GB for Confluence.For heavy use, consider setting it to 4GB or more.
If you are migrating from
innodb_log_file_sizetoinnodb_redo_log_capacity, set the capacity to:innodb_log_file_size × innodb_log_files_in_group
Additional resources
Was this helpful?