Bug #41621 ndb tests fail sporadically: 274 'Time-out in NDB, probably caused by deadlock'

• Submitted: 19 Dec 2008 7:05
• Reporter: Sven Sandberg
• Status: Verified
• Category: Tests: Cluster
• Severity: S7 (Test Cases)
• Version: 5.1, 6.0
• OS: Any
• CPU Architecture: Any
• Tags: deadlock, ndb, pushbuild, sporadic, test failure, warning

[19 Dec 2008 7:05] Sven Sandberg

Description:
The following warning pops up in random ndb tests in pushbuild:

ndb.ndb_lock_table             [ fail ]

--- /data0/pushbuild/pb/bzr_mysql-6.0-falcon/121/bzr_mysql-6.0-falcon-exp/mysql-test/suite/ndb/r/ndb_lock_table.result	2008-12-15 15:48:05.000000000 +0300
+++ /data0/pushbuild/pb/bzr_mysql-6.0-falcon/121/bzr_mysql-6.0-falcon-exp/mysql-test/suite/ndb/r/ndb_lock_table.reject	2008-12-16 04:42:47.000000000 +0300
@@ -1,3 +1,5 @@
+Warnings:
+Warning	1297	Got temporary error 274 'Time-out in NDB, probably caused by deadlock' from NDB
 drop table if exists t1;
 create table t1 (a int) engine ndb;
 set autocommit=1;

mysqltest: Result length mismatch

Stopping All Servers

How to repeat:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-falcon&order=121 sapsrv1/rpl_ndb_row
xref: http://tinyurl.com/4eghcx

[19 Dec 2008 7:28] Stewart Smith

likely not a bug.

machines heavily loaded will generate spurious timeouts.

only workaround is to increase (even more) the timeout config options

[19 Dec 2008 12:38] Sven Sandberg

An alternative may be to add a suppression for that warning for all ndb tests, unless you think that will hide real errors.