Hello Jose,
If MySQL server (mysqld) is crashing, and not the instance itself, it could be a utilization issue. Hence, you may check the corresponding graph in the instance overview page, and for testing purposes you may try migrating with a higher CPU/Memory type machine (you have the ability to downgrade after).
But are you sure that the crash is causing the connection issue (could be not related)? For example, and while you replicated the server locally (and not over the internet), it could also (in addition to crashing) be a connection issue like this communication error, and per this troubleshooting guide , this does not indicate that you have an issue with the Cloud SQL instance itself, but the "application is not terminating connections properly", or caused by a network issue.
On the other hand, and while this is affecting one table, and as you have a special case using named pipes, it would be nice to investigate it through issue tracker. Opening a report, make sure it is private, include your project ID, instance name, all error messages for the behavior described above, and detailed reproduction steps.
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/af44d1d8-fe41-4d26-8c73-81756e43d9a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment