"drop database" Command Kills CloudSQL Instance

[david....@o3apps.com]

Recently, we created a new CloudSQL instance and are currently working through the configuration of a new GAE application. During the initial setup we have needed to drop the database and recreate it several times, however, each time we do the CloudSQL instance hangs and requires a full restart through the console.

Has anyone else encountered this issue? If so, what is the best course of action?

Thanks!

[Razvan Musaloiu-E.]

Can you please elaborate on what do you mean by 'instance hangs'? You establish new connections? The already establish stopped working? If you have a working established connection you can use SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS to take a look what is going on. Another good to keep in mind: dropping a database requires obtaining some a global lock on the whole table.

-- Razvan ME

--
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-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/caae4c86-41f9-4faf-911b-9a7085f4204a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[david....@o3apps.com]

Razvan,

Here is some additional detail:

Instance hangs = From the cmd line the command is given and simply never returns. While the server is "hanging" on the drop db request new connections are acknowledged by the server, however, additional statements/commands submitted will not return a result. From the MySQL Workbench application the command is given and after a period of time the workbench application stops functioning.

After the instance is restarted via the Google Cloud portal the database will successfully drop but if another drop command is given the issue resurfaces again.

Thanks for your time.

[Razvan Musaloiu-E.]

Things are not quite clear yet for me. Can you please do the following test:

• establish two connections (A and B)
• on connection A do the DROP DATABASE
• on connection B do an SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS

-- Razvan ME

--

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-d...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/1eba11a4-9b48-4235-a3f4-63ae25f70bb2%40googlegroups.com.

[Amit Mondal]

I see that you mention additional new connection is acked by server but statement does not return result. This hints me that it likely to a MySQL level issue with locks etc. Please follow Razvan's instruction for debugging the issue.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CA%2BUvTg2guOuSGxwHnEFDG2e-2-0oqpZcYLB-AjOOuCdXN8Cz2A%40mail.gmail.com.