Rollback Failure After Upgrading to a Later Version When Instant ADD COLUMN Has Caused Page Data Usage to Exceed 50%
Last updated:2025-12-24 16:09:19
Rollback Failure After Upgrading to a Later Version When Instant ADD COLUMN Has Caused Page Data Usage to Exceed 50%
Last updated: 2025-12-24 16:09:19
Issue
After an upgrade to a later kernel version, the rollback fails when instant ADD COLUMN has caused page data usage to exceed 50%.
Issue Triggering Scenarios
MySQL 8.0 20221221 and earlier versions allow instant ADD COLUMN operations even when the row size exceeds half the page size. After a kernel version upgrade, a rollback failure may occur due to row size exceeding the limit during the rollback.
Affected Kernel Versions
MySQL 8.0 20221221 and earlier versions.
Fixed Kernel Version
MySQL 8.0 20241005.
Check Methods
You can refer to the following commands to check for tables with potential risks.
select replace(name, '/', '.') as 'table_schema.table_name' from information_schema.innodb_tables where TOTAL_ROW_VERSIONS!=0 or INSTANT_COLS!=0;
Fixing Methods
1. Upgrade the kernel version to MySQL 8.0 20241005. For the operation method, see Upgrading the Kernel Minor Version.
2. After a kernel version upgrade, rebuild and repair the corrupted tables. You can use the method
alter table xx engine = innodb; for repair. To avoid business impact caused by table locking, it is recommended to perform the repair during off-peak hours using tools such as pt-osc.Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback