Hi,
Before migration to GC we had no issues with this even on much larger data sets. Since the application's codebase didn't change nor the dataset increased too much, the issue seems to be related to a) mysql settings b) version of mysql c) server setup - because that's what was changed as result of migration.
Since the issue seems to be resolved I can't spend too much time on this now but I'll try to prepare a test data set so it is easy to reproduce the issue and share it with you.
best,
-- you could say the data set is large (~10G) but the particular query that caused troubles is using a temporary table with just a fraction of the entire table. It is using JOIN but I'm 99% sure that we had the same error on a query with just a single, relatively small table.
Before migration to GC we had no issues with this even on much larger data sets. Since the application's codebase didn't change nor the dataset increased too much, the issue seems to be related to a) mysql settings b) version of mysql c) server setup - because that's what was changed as result of migration.
Since the issue seems to be resolved I can't spend too much time on this now but I'll try to prepare a test data set so it is easy to reproduce the issue and share it with you.
best,
Ann
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/583959b1-1dca-44fe-b066-f5a2c757f2e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment