Crash Caused by Instant ADD COLUMN Followed by Online DDL on the Same Table
Last updated:2025-12-24 16:09:19
Crash Caused by Instant ADD COLUMN Followed by Online DDL on the Same Table
Last updated: 2025-12-24 16:09:19
Issue
Performing an instant ADD COLUMN operation followed by an online DDL operation on the same table causes a crash.
Issue Triggering Scenarios
If an instant DDL operation is performed on a table, immediately followed by an online DDL operation such as OPTIMIZE TABLE or ALTER TABLE .. ADD PRIMARY KEY, a program crash may occur. This is because the code fails to handle the scenario correctly (failing to add columns or the REDUNDANT format).
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