2017-02-10T16:02:22.555549Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
It appears that the instance had a lock that was held for more than 5 minutes and innodb crashed the server because of that. It's possible there was a deadlock happening.
In order to prevent this in the future we recommend looking over your current queries to see if any could cause a deadlock.
This is the answer from them, so at the time this happened we were running a migration, which was making a connection to sql, accessing 100 databases, altering few tables, closing connection, connecting again, accessing the next 100 databases, doing the changes etc etc...
We have around 13 000 databases. So this occurred when the script was working on 6600th databases.
I was disconnecting and connecting every 100 databases, so the timeout wont bother me again, but again we were deadlocked.
And the greatest issue is that google cloud shows the status of the cloud instance green, as if everything is just good. But you can't access to the instance, and you can't restart, reset, start/stop it because you always see An unknowsn error ocurred in Operations tab.
We still waiting for them to respond, 3 hours passed, no response from them, and we losing tones of money because of this.
We even bought the gold support package, so we get answers faster ... still nothing. Too much disappointed in services, really
-- It appears that the instance had a lock that was held for more than 5 minutes and innodb crashed the server because of that. It's possible there was a deadlock happening.
In order to prevent this in the future we recommend looking over your current queries to see if any could cause a deadlock.
This is the answer from them, so at the time this happened we were running a migration, which was making a connection to sql, accessing 100 databases, altering few tables, closing connection, connecting again, accessing the next 100 databases, doing the changes etc etc...
We have around 13 000 databases. So this occurred when the script was working on 6600th databases.
I was disconnecting and connecting every 100 databases, so the timeout wont bother me again, but again we were deadlocked.
And the greatest issue is that google cloud shows the status of the cloud instance green, as if everything is just good. But you can't access to the instance, and you can't restart, reset, start/stop it because you always see An unknowsn error ocurred in Operations tab.
We still waiting for them to respond, 3 hours passed, no response from them, and we losing tones of money because of this.
We even bought the gold support package, so we get answers faster ... still nothing. Too much disappointed in services, really
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/d558e44e-3e20-4ead-80ef-acba580975bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment