MySQL Bugs: #18952: NDB Auto Discovery is failing designed tests in ndb

Bug #18952	NDB Auto Discovery is failing designed tests in ndb_autodiscovery.test
Submitted:	10 Apr 2006 15:56	Modified:	26 Dec 2006 17:33
Reporter:	Lars Thalmann
Status:	Verified
Category:	Server: Cluster	Severity:	S3 (Non-critical)
Version:	mysql-5.1	OS:	Any
Assigned to:	Martin Skold	Target Version:	CGE
Tags:	disabled, ndb, test failure, 5.1 bk, 5.1-Telco, ndb_autodiscover
Triage:	Triaged: D3 (Medium)

Description:
jmiller 1.74    ndb_autodiscover        : Needs to be fixed w.r.t binlog
jmiller 1.74    ndb_autodiscover2       : Needs to be fixed w.r.t binlog

How to repeat:
Check disabled.def

Verified just as described with 5.1.10-BK (ChangeSet@1.2303.1.1, 2006-04-09
19:43:36-07:00)

this is disabled because ndb handler cannot handle explicit remove of frm

Hi,

I took a look at this today and it seems the auto discovery has changed. The test now
fails on each sub test unless you add a "show tables" right after the frm removal. Not
sure this is the was auto discovery is supposed to be working.

/jeb

create table t1(
  id int not null primary key,
  name char(20)
) engine=ndb;

insert into t1 values(1, "Autodiscover");
flush tables;
--remove_file $MYSQLTEST_VARDIR/master-data/test/t1.frm
select * from t1;
show status like 'handler_discover%';

Errors are (from /data1/mysql-5.1-telco2/mysql-test/var/log/mysqltest-time) :
mysqltest: At line 28: query 'select * from t1' failed: 1105: Failed to open 't1', error
while unpacking from engine

#
# Test discover + INSERT
#

flush tables;
--remove_file $MYSQLTEST_VARDIR/master-data/test/t1.frm
insert into t1 values (2, "Auto 2");
show status like 'handler_discover%';
insert into t1 values (3, "Discover 3");
show status like 'handler_discover%';
flush tables;
--remove_file $MYSQLTEST_VARDIR/master-data/test/t1.frm
select * from t1 order by id;
show status like 'handler_discover%';

Errors are (from /data1/mysql-5.1-telco2/mysql-test/var/log/mysqltest-time) :
mysqltest: At line 38: query 'insert into t1 values (2, "Auto 2")' failed: 1105: Failed
to open 't1', error while unpacking from engine

This trend continues through the test case. Note, if you do a SHOW TABLES before the
select, insert, update, etc... then the test passes.