Cloud SQL instance stuck in "Instance is being updated" status for more than two hours

Google Cloud Database
1

My MySQL instance stayed in the “Instance is being updated” state for more than two hours.

I would like to add that the operation I performed was to start the instance.

TonyCe_0-1747327657279.png
TonyCe_0-1747327657279.png1398×322 26.8 KB

2

Hi @TonyCe ,

Welcome to Google Cloud Community!

It looks like your MySQL instance might be stuck for a few reasons:

  • Maintenance Delays: If your instance was stopped during a scheduled maintenance update, Cloud SQL would skip the update. However, the next time you restart your instance, it will automatically apply the latest update, which could be why it’s still stuck in the “being updated” state.
  • Stuck Backup: If your backup has been running for hours and can’t be canceled, it might be due to the size of the database. Backups can take a while, but if you really need to cancel it, you can reach out to Google Cloud support to force a restart.
  • Temporary Data Buildup: If your instance is stuck due to large temporary data (like too many temporary tables being created), the ibtmp1 file could have grown large. Unfortunately, the only way to shrink it is by restarting the service. To avoid this in the future, you could create temporary tables with ROW_FORMAT=COMPRESSED, though it may affect performance.
  • Disk Space Issues: If your instance ran out of disk space and the automatic storage increase isn’t enabled, your instance could have gone offline. You can fix this by enabling the automatic storage increase feature in your instance settings.

If none of these are the issue, it might be a good idea to contact Google Cloud support for further help.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.