MySQL upgrade to second generation fails

[Allen Firstenberg]

We are trying to upgrade our MySQL 1st Generation instances to the 2nd Generation ahead of the forced upgrade next year. We created a clone of the original to test the process out.

The database is about 121GB on a D4 instance with all preconditions met.

After the upgrade runs for about 8 hours, it fails with an error

Timed out while running mysql upgrade. Please try increasing instance to a larger tier and retry.

It then lists a number of our tables, indicating "Failed to ALTER TABLE" and that it "Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)".

It concludes with the message

Failed to run mysql_upgrade, please refer to the documentation.

As it suggested, we increased it to a D8 instance, and tried it again, to the same result. We then increased it to a D32 instance, with the same result.

There is nothing we can find in the documentation about upgrading to the 2nd generation or mysql_upgrade to suggest how we should proceed.

Does anyone have any suggestions about how we can go about debugging and correcting this problem so we can upgrade?

[Harmit Rishi (Cloud Platform Support)]

Hello, 

After some research, I was not able to find anything that would cause the issues you have mentioned during the migration process. Given that the deadline for this action is looming, I believe the appropriate action at this point would be to have support take a look at the affected instance. 

You may feel free to create a private issue with us on our Public Issue Tracker here. Creating a private issue will ensure that your specific instance details will not be shared with the public. 

I look forward to hearing from you there!