Re: Lock wait timeout exceeded; try restarting transaction
The units for lock time (like most times in MySQL) is seconds (elapsed, not cpu). Profiling may be different.
18446744073709.550781 -- this is bogus. Take a look at the value of 2**64. I have been plagued with that number in the slowlog. It is as if the clock ran backwards, and underflowed in an UNSIGNED BIGINT.
Do you have an example without that bogus number?
"Query_time: 0.000330" = 0.33ms = 330us -- this feels reasonable for a 2-row select of a table that is cached.
3us? That's extremely fast. I would expect the lag getting to the server, parsing the query, etc, to be more than that. Did you mean 3ms?
Back to autocommit -- could you turn on the binlog and/or general log. Are there any BEGIN (or START) and COMMIT commands in the binlog or general log?
I'm worried that some _other_ connection has autocommit ON and is doing a query then sitting idle (perhaps due to a "persistent" connection) for more than 30 seconds.
What version of MySQL are you using? Are you using the InnoDB Plugin?
Can you turn on Profiling and see what it gives you?
Subject
Views
Written By
Posted
12238
June 04, 2010 10:07PM
5137
June 05, 2010 12:43AM
3234
June 06, 2010 09:01AM
4251
June 06, 2010 10:39AM
3087
June 06, 2010 08:17PM
2508
June 06, 2010 08:37PM
3845
June 07, 2010 05:53PM
2914
June 08, 2010 01:23AM
3147
June 08, 2010 01:52AM
2106
June 08, 2010 09:02AM
3024
June 08, 2010 12:55PM
1885
June 09, 2010 12:49AM
3086
June 10, 2010 11:22PM
Re: Lock wait timeout exceeded; try restarting transaction
3452
June 11, 2010 09:25AM
3074
June 11, 2010 04:04PM
1794
June 11, 2010 08:02PM
3093
June 15, 2010 07:27PM
7310
June 15, 2010 08:13PM
2533
June 15, 2010 11:02PM
2388
June 15, 2010 11:04PM
3171
June 15, 2010 11:17PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.