1+N环境MySQL8.0.29/30版本BUG处理措施

背景：
前期安全漏扫后，1+N环境中部分MySQL8.0数据库由低版本通过upgrade方式升级到8.0.29版本，后又升级到8.0.30版本。此版本的upgrade升级方式，在执行 alter table add colmun 操作时有一定几率会触发MySQL内部BUG，导致数据库崩溃。
注意：MySQL8.0.29版本有重大BUG，MySQL官方已收回此版本，官网已不提供下载，需升级到最新版本

主机业务范围略

 

应急措施：
1、上述环境涉及的业务系统，在BUG正式修复之前，暂时先不要执行  alter table add colmun 操作命令，统一提交给DBA执行。
2、需要执行该操作的，可在本贴中回复，或直接联系 
3、待数据库升级完毕、该BUG修复后，方可再自主执行。

 

相关BUG信息： 
 

• InnoDB: After upgrading to MySQL 8.0.29, a failure occurred when attempting to access a table with an instantly added column. (Bug #34233264)

• InnoDB: After upgrading to a release that supports row versions for columns added or dropped using ALGORITHM-INSTANT, a failure occurred during an instant ADD COLUMN operation on a table with a nullable column and an instantly added column. (Bug #34488482)

• InnoDB: The physical position of columns were not set correctly after dropping a column and renaming an existing column to the name of the dropped column. (Bug #34463089)

• InnoDB: A column added using ALGORITHM=INSTANT was visible in read views created before the DDL operation that added the column. (Bug #33937504)