Bug #38085 rpl_ndb.rpl_ndb_basic: 'Lock wait timeout exceeded...' At line 8

• Submitted: 13 Jul 2008 15:38
• Modified: 12 Mar 2009 14:34
• Reporter: Andrei Elkin
• Status: No Feedback
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• OS: Any
• CPU Architecture: Any
• Tags: pushbuild, sporadic, test failure

[13 Jul 2008 15:38] Andrei Elkin

Description:
mysqltest: In included file "./include/ndb_not_readonly.inc": At line 8: query 'delete from mysql.ndb_apply_status where server_id=0' failed with wrong errno 1205: 'Lock wait timeout exceeded; try restarting transaction', instead of 0...

The result from queries just before the failure was:
ERROR HY000: Lock wait timeout exceeded; try restarting transaction

More results from queries before failure can be found in /dev/shm/var-rpl_ndb_row-121/log/rpl_ndb_basic.log

Warnings from just before the error:
Error 1297 Got temporary error 266 'Time-out in NDB, probably caused by deadlock' from NDB

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?startdate=&enddate=&dir=&plat=sapsrv1&...
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-bugteam&order=49 bzr_mysql-6.0-bugteam/49sapsrv1/rpl_ndb_row

[12 Feb 2009 14:34] Jonathan Miller

Does this still happen?

[13 Mar 2009 0:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".