There are several possible causes for the "Lost connection to MySQL server at 'reading initial communication packet'" error:
-- - This occurs if your GCE instance's IP address is not authorized to access the Cloud SQL instance. I doubt this is the case because it would not be an intermittent error.
- This error also occurs if your instance is unavailable, for example because it is taking a long time to restart or start. If you instance has "on demand" activation, you might want to try "always on" mode and see if that helps. Long restart times can also be caused by a large general log; If you have ever had it enabled try truncating the general log.
- This message might occur if you are hitting one of the connection limits. Take a look at the "active connections" graph for your instance on the developers console, does it show a lot of connections when you get the error?
- Do you open and close connections extremely frequently? This can cause you to hit a connection limit even if the total number of concurrent connections does not increase too far.
Also remember the occasional error connection to Cloud SQL is expected. Please review the Cloud SQL SLA to get an idea of the error rate we aim for.
Yours,
David
On Fri, Oct 30, 2015 at 1:54 AM, Joakim <joakim@biddl.com> wrote:
--We have a Django Application (hosted on Compute Engine), that uses Cloud SQL. We've set up really frequent monitoring of it in the Load Balancers health checks. We do however about once per day get a bunch of the following errors: django.db.utils:OperationalError: (2013, 'Lost connection to MySQL server at \'reading initial communication packet\', system error: 0 "Internal error/check (Not system error)"').Typically the MySQL/Cloud SQL interaction of the health checks takes less than 20ms, however a few times a day the it can suddenly take 500-1200 ms.The database is really lightly loaded (health checks count for > 95% of the requests to the system) and we've not seen any similar issues during heavy load testing. There just seems to be something randomly causing Cloud SQL to perform really slowly for a request or two or drop the connections and then continue to work normally.What could be the reason to both loosing the connection and to the random, but extreme slowness? Any ideas on how to possibly fix both issues?
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/21b7c9b2-eee6-459c-9b69-ba7d2fcbd740%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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/CAJZK_bbbHc2dPjmbDZ9rOZW8v9ROrwFER180g%2Byb%2BuTLGRF65A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
