Issue Summary

Since MySQL 8.0.33, the parameter innodb_redo_log_capacity is an extension of the original innodb_log_file_size parameter, with the first overriding the latter, as per MySQL Documentation. Confluence database healthcheck still uses innodb_log_file_size, leading to a false healthcheck failure.

Steps to Reproduce

1. Deploy any Confluence version with the database healthcheck and MySQL 8.0.33 or above
2. Ensure the paremeter innodb_redo_log_capacity is above 256MB
3. Navigate to Confluence administration > Troubleshooting and support tools > Instance health tab

Expected Results

Healthcheck should be successful, no issues reported regarding the innodb file size limit.

Actual Results

Database healthcheck fails due to "InnoDB Log File Size" with the following message:
"Your innodb_log_file_size of 48MB is too small. You should increase innodb_log_file_size to 256M.". 

Workaround

No workaround is necessary as only the healthcheck is affected by this problem. But we recommend double-checking the effective innodb log size in your database:

SHOW GLOBAL VARIABLES LIKE ‘innodb_redo_log_capacity’;