Bug #38087 rpl_truncate_7ndb failed at At line 15: replace into mysql.ndb_apply_status
Submitted: 13 Jul 2008 16:01 Modified: 12 Mar 2009 14:35
Reporter: Andrei Elkin Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: pushbuild, sporadic, test failure

[13 Jul 2008 16:01] Andrei Elkin
Description:
CURRENT_TEST: rpl_ndb.rpl_truncate_7ndb
mysqltest: In included file "./include/ndb_not_readonly.inc": At line 15: query 'replace into mysql.ndb_apply_status values(0,0,"",0,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-ps_row-112/log/rpl_truncate_7ndb.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-rpl&order=24
[13 Jul 2008 16:05] Andrei Elkin
A similar failure with another test:

CURRENT_TEST: rpl_ndb.rpl_ndbapi_multi
mysqltest: In included file "./include/ndb_not_readonly.inc": At line 15: query 'replace into mysql.ndb_apply_status values(0,0,"",0,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:
Warnings:
Error	1297	Got temporary error 274 'Time-out in NDB, probably caused by deadlock' from NDB
ERROR HY000: Lock wait timeout exceeded; try restarting transaction

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-rpl&order=24
[12 Feb 2009 14:35] Martin Skold
Is this still an issue?
[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".