Stored Procedure disappearing in Google Cloud SQL - 1st Generation Instance

Visto 471 veces
Saltar al primer mensaje no leído

Dhandapani Sattanathan

no leída,
7 dic 2016, 2:17:567/12/16
a Google Cloud SQL discuss
Cloud SQL Team,

Past 3 years I 'm using Google Cloud SQL with Google App Engine.

In My development instance, most of the time lastly ran stored procedure disappearing. I thought it's development instance, We got proc table crashing.Some other reason stored procedure disappearing.

But In My Production instance, Two stored procedure recently ran disappeared.Because of this, We got a big issue in my production.

Could you please explain Why like this happening in Google Cloud SQL 1st Generation instance?

Thanks in advance.


David Newgas

no leída,
7 dic 2016, 12:17:287/12/16
a Google Cloud SQL discuss
Hi,

Without investigating in greater detail, I believe the most likely cause is that the mysql.proc table as you mention. The reason that this can occur is that MySQL 5.x only supports MyISAM for the mysql.* tables, but MyISAM can lose data across a crash/hard restart. I believe the best solution is to run a FLUSH TABLES operation after creating/changing stored proceedures/events/triggers etc, to make sure that they have been written to disk and will survive any future restarts.

David

--
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+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/daf127a4-08d1-4d79-a197-8c215c02b40d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Dhandapani Sattanathan

no leída,
8 dic 2016, 22:33:278/12/16
a Google Cloud SQL discuss
Hi David,

Thanks for your reply. I told mysql.proc table crashing in my development instance. But Production instance I never get any crash in mysql.proc table.

Development instance and Production instance both are different. I asked after investigation only.

There was no mysql.proc table crash.  I 'll try your solution to run a FLUSH TABLES operation after creating/changing stored procedures/events/triggers etc. 

Thanks David.
Responder a todos
Responder al autor
Reenviar
0 mensajes nuevos