Wednesday, March 20, 2013

Re: Error 1205: Lock wait timeout exceeded; try restarting transaction

I don't see anything unusual with your instance. Are you doing any queries that grab the same locks? Can you investigate using SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS using the command line tool?

-- Razvan ME


On Wed, Mar 20, 2013 at 6:17 PM, Carl Schroeder <schroeder.carl.j@gmail.com> wrote:
lemurspot-project:lemur-prime is the instance name


On Wednesday, March 20, 2013 5:57:51 PM UTC-7, Razvan Musaloiu-E. wrote:
Can you tell us your instance name?

-- Razvan ME


On Wed, Mar 20, 2013 at 5:48 PM, Carl Schroeder  wrote:

Error 1205: Lock wait timeout exceeded; try restarting transaction 
Just started getting these this afternoon. This is in the Google APIs console "SQL Prompt" window on deletes and updates.
I am 82MB into my 100GB limit.
Using python from app engine fails silently when trying to update. Very distressing.
Anyone have any ideas?

--
 
 

--
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

No comments:

Post a Comment