Bug #50472 In LM_READ scans wait for uncommited inserts
Submitted: 20 Jan 2010 12:45
Reporter: Andrew Hutchings Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: CPU Architecture:Any
Triage: Triaged: D3 (Medium) / R6 (Needs Assessment) / E6 (Needs Assessment)

[20 Jan 2010 12:45] Andrew Hutchings
Description:
As subject.

How to repeat:
create table t1 (
a bigint(18) NOT NULL AUTO_INCREMENT primary key,
b varchar(128) NOT NULL,
c LONGTEXT
) ENGINE NDB ;

mysql1> set autocommit=0;
mysql1> insert into t1 (b,c) values ('test','test');

mysql2> select * from t1;

ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction
mysql2> show warnings\G
*************************** 1. row ***************************
  Level: Error
   Code: 1297
Message: Got temporary error 274 'Time-out in NDB, probably caused by deadlock' from NDB
*************************** 2. row ***************************
  Level: Error
   Code: 1297
Message: Got temporary error 274 'Time-out in NDB, probably caused by deadlock' from NDB
*************************** 3. row ***************************
  Level: Error
   Code: 1205
Message: Lock wait timeout exceeded; try restarting transaction
*************************** 4. row ***************************
  Level: Error
   Code: 1622
Message: Storage engine NDB does not support rollback for this statement. Transaction rolled back and must be restarted
4 rows in set (0.00 sec)