Bug #7656 'create table' fails at test start
Submitted: 4 Jan 2005 11:10 Modified: 21 Jan 2005 7:34
Reporter: Joerg Bruehe Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:5.0.3-pre OS:Open BSD 3.6
Assigned to: Tomas Ulin CPU Architecture:Any

[4 Jan 2005 11:10] Joerg Bruehe
In a 'max' build, all tests fail that have a 'create table' as the first orsecond statement. The typical symptom is:

*** r/compare.result    Fri Dec 31 20:00:11 2004
--- r/compare.reject    Sat Jan  1 07:09:36 2005
*** 1,5 ****
--- 1,7 ----
  drop table if exists t1;
  CREATE TABLE t1 (id CHAR(12) not null, PRIMARY KEY (id));
+ Warnings:
+ Error 1296    Got error 4009 'Cluster Failure' from NDB
  insert into t1 values ('000000000001'),('000000000002');
  explain select * from t1 where id=000000000001;
  id    select_type     table   type    possible_keys   key     key_len ref     rows    Extra

This makes most of the test suite fail.
The effect is specific to machine 'ds9', not noticed anywhere else (in this run).

To me, it appears similar to bug#7625.

How to repeat:
Run the test suite with a 'max' build on 'ds9'
[21 Jan 2005 7:34] Tomas Ulin
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

works ok in jan-20 -max build