Bug #35638 ndb_condition_pushdown fails with Time-out in NDB
Submitted: 28 Mar 2008 10:57 Modified: 12 Mar 2009 14:13
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
Triage: Needs Triage: D4 (Minor)

[28 Mar 2008 10:57] Andrei Elkin
Description:
According to xref history it happened twice

https://intranet.mysql.com/secure/pushbuild/getlog.pl?dir=mysql-5.0-engines&entry=rkalimul...
https://intranet.mysql.com/secure/pushbuild/getlog.pl?dir=mysql-5.0-rpl&entry=zhe@mail.hez...

with mtr's log:

ndb_condition_pushdown         [ fail ]

--- /data0/pushbuild/pb/mysql-5.0-rpl/222/mysql-5.0-rpl-exp/mysql-test/r/ndb_condition_pushdown.result	2008-03-27 08:52:57.000000000 +0300
+++ /data0/pushbuild/pb/mysql-5.0-rpl/222/mysql-5.0-rpl-exp/mysql-test/r/ndb_condition_pushdown.reject	2008-03-27 09:24:56.000000000 +0300
@@ -542,6 +542,8 @@
 order by auto;
 auto
 1
+Warnings:
+Error	1296	Got error 274 'Time-out in NDB, probably caused by deadlock' from NDB
 explain
 select auto from t1 where 
 string != "aaaa" and 

How to repeat:
See pb's log via xref.

The failure looks to be of very low profile.
[12 Feb 2009 14:13] Martin Skold
IS this still occuring?
[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".