Hi all,
The migration process is simple: Two processes are started and communicate via a named pipe. One reads records from oracle and writes them in CSV form to the pipe. The other one just issues a "load data infile..." reading from the named pipe.
I start the migration process and, after some minutes migrating rows, the writing process stops due to a broken pipe exception, the reading process (that reads from the named pipe and loads data into MySQL) has stopped, being disconnected from the MySQL connection. After some try-and-error, I've found that, when that happens, if I query uptime to the MySQL server ("show global status like 'Uptime'"), it's reset (that is: the service has restarted)
Logfiles (stack driver) also confirm this: seconds after the migration process fails, there are traces of MySQL starting and finding it didn't shut down properly the last time.
Any one else has experienced something like this?
Any hint on how to get this debugged and see if I've stumbled upon some platform/MySQL bug?
This doesn't happen if I replicate the table to a local MySQL or if I replicate another table to the same Cloud SQL MySQL instance. Looks like a specific issue with the MySQL Google Cloud service and some content in this table.
Right now I'm trying to identify whether the issue is due to a specific row/column of the input data source, but any help or experience about this will be welcome.
Best,
Jose
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/29f00f21-c7b7-4f6e-9da1-cdda45136121%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment