Friday, July 17, 2020

[google-cloud-sql-discuss] Re: Cloud SQL Read Replica Legging behind master

This documentation[1] gives hints on the possible causes of replication lag, especially when they are consistently high. The replication delay often indicate that write workload may be too high for the replica to handle. I have seen situations in the past where the replication delay was a result of consistently handling workloads with CPU intensive queries (sorting, regular expressions, other complex functions). As explained in this documentation[2], CPU intensive queries often make the CloudSQL instance to be throttled.

For better understanding or the exact details of what may be happening on your CloudSQL Instance, I recommend you contact the GCP Support[3]. This way a GCP Support Engineer would be able to review the specific details on your CloudSQL with you.


[1]https://cloud.google.com/sql/docs/mysql/replication/tips#highlag
[2]https://cloud.google.com/sql/docs/mysql/diagnose-issues#tips
[3]https://cloud.google.com/support-hub

--
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/514a7b74-681c-41af-90e7-9d8181ec92f1o%40googlegroups.com.

No comments:

Post a Comment