ETA on Fix for MySQL 8.0.29 Corruption Issue

5

I just received this email:

"Hello, You are receiving this message because you have one or more Amazon RDS for MySQL instances running version 8.0.29. The MySQL 8.0.29 community release has introduced a new regression in the InnoDB storage engine [1] which causes the MySQL database process to crash after new columns are added or dropped using the INSTANT DDL algorithm [2]. To prevent customers from experiencing this issue, we no longer allow creating new instances using RDS for MySQL 8.0.29, or, upgrading existing instances to version 8.0.29. Your Amazon RDS instances running MySQL 8.0.29 are listed in "Affected Resources" tab of the AWS Health Dashboard. On these existing RDS for MySQL 8.0.29 instances, we recommend that you avoid adding/removing new columns using the INSTANT DDL algorithm. If you observe visible symptoms of a crash on your RDS for MySQL 8.0.29 instance, we recommend you perform a Point-In-Time-Restore [3] to recover the database to a time before the first process crash was reported in the logs or before any column changes were made to the database.

If you have questions or concerns, the AWS Support Team is available on AWS re:Post [4] and via Premium Support [5].

[1] https://forums.mysql.com/read.php?22,704532,704532#msg-704532 [2] https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-operations.html#online-ddl-column-operations [3] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIT.html [4] https://repost.aws/ [5] https://aws.amazon.com/support

"

MySQL 8.0.30 was released today with a fix for this issue. https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html https://forums.mysql.com/read.php?22,704532,705126#msg-705126

When will MySQL 8.0.30 be available in the AWS RDS console?

asked 2 years ago362 views
1 Answer
3

Still no word on a timeline? It's been two weeks, and all RDS snapshots taken on 8.0.29 are completely unusable and unrecoverable. AWS' proposed solution is a point-in-time restore to 8.0.28, but in our case, that means losing all data since April, which makes no sense as a valid workaround. I'm sure we're not the only ones in this camp. AWS' silence on this matter is anything but reassuring. We need some degree of transparency so we can plan accordingly--at minimum, an approximate timeline. RDS isn't cheap; why do we have to feel as though we're fighting for basic access to our backups?

paul
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions