![]() Furthermore, if updates were made to those jobs during the replication phase, the migration job may fail.ĭescription: Our engineering team continues to investigate the issue caused by a MySQL bug that may affect customers who migrated to MySQL 5.7.36 on or after November 2nd 2021, from a source database that had gtid_mode set to ON. The mitigation is expected to complete over the next few days.ĭiagnosis: Cloud SQL External Server or Database Migration Service (DMS) users who migrate to Cloud SQL for MySQL 5.7 with GTID replication using managed dumps may experience errors if they have insert/update/delete transactions during the dump phase. Summary: Global: Issues with Cloud SQL for MySQL instance migration to 5.7 when source databases have gtid_mode set to ON.ĭescription: Mitigation work is still underway by our engineering team. We thank you for your patience while we worked on resolving the issue. We will be sending out targeted communications to the affected customers. New instances will no longer experience this issue, but please follow the recommended workaround for existing instances that are impacted. The issue with Cloud SQL has been resolved as of Thursday, 12:25 US/Pacific. Workaround: Customers should start a new migration by dumping the data from a source database instance running MySQL 5.7.35 or lower versions to Google Cloud Storage (GCS) manually (Cloud SQL, DMS), using a mysqldump file, and then migrate using the dump file to Cloud SQL for MySQL 5.7. New instances should not experience this issue, but please follow the below recommended workaround for existing instances that are impacted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |