Saturday, November 23, 2013

Re: "drop database" Command Kills CloudSQL Instance

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


On Sat, Nov 23, 2013 at 6:16 PM, <david.nielson@o3apps.com> wrote:
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.

--
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/1eba11a4-9b48-4235-a3f4-63ae25f70bb2%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg2guOuSGxwHnEFDG2e-2-0oqpZcYLB-AjOOuCdXN8Cz2A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment