diff options
author | unknown <tomas@poseidon.ndb.mysql.com> | 2006-05-18 23:38:07 +0200 |
---|---|---|
committer | unknown <tomas@poseidon.ndb.mysql.com> | 2006-05-18 23:38:07 +0200 |
commit | f87e68e45fa4954a2c222864daec89f54d60b3aa (patch) | |
tree | 02ea74c59357b89e35c1d64e7f08a79bd10842b7 /mysql-test/t/ndb_autodiscover3.test | |
parent | ea7cc4af64a886651fe57eb2077bdf628a8b7dc9 (diff) | |
download | mariadb-git-f87e68e45fa4954a2c222864daec89f54d60b3aa.tar.gz |
Bug #19395 mysqld does not always detect cluster shutdown
Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak
mysql-test/r/ndb_autodiscover3.result:
Bug #19395 mysqld does not always detect cluster shutdown
mysql-test/t/disabled.def:
Bug #19395 mysqld does not always detect cluster shutdown
mysql-test/t/ndb_autodiscover3.test:
Bug #19395 mysqld does not always detect cluster shutdown
sql/ha_ndbcluster_binlog.cc:
Bug #19395 mysqld does not always detect cluster shutdown
storage/ndb/include/ndbapi/Ndb.hpp:
Bug #19395 mysqld does not always detect cluster shutdown
storage/ndb/include/ndbapi/NdbDictionary.hpp:
Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak
storage/ndb/src/kernel/blocks/suma/Suma.cpp:
Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak
storage/ndb/src/ndbapi/Ndb.cpp:
Bug #19395 mysqld does not always detect cluster shutdown
storage/ndb/src/ndbapi/NdbEventOperationImpl.cpp:
Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak
storage/ndb/src/ndbapi/NdbEventOperationImpl.hpp:
Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak
Diffstat (limited to 'mysql-test/t/ndb_autodiscover3.test')
-rw-r--r-- | mysql-test/t/ndb_autodiscover3.test | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/mysql-test/t/ndb_autodiscover3.test b/mysql-test/t/ndb_autodiscover3.test index afbebc4dd03..ed75c89cdd1 100644 --- a/mysql-test/t/ndb_autodiscover3.test +++ b/mysql-test/t/ndb_autodiscover3.test @@ -43,6 +43,7 @@ select * from t2 order by a limit 3; --error ER_NO_SUCH_TABLE select * from t2; show tables like 't2'; +reset master; create table t2 (a int key) engine=ndbcluster; insert into t2 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10); select * from t2 order by a limit 3; @@ -50,6 +51,7 @@ select * from t2 order by a limit 3; # server 1 should have a stale cache, and in this case wrong frm, transaction must be retried --connection server1 select * from t2 order by a limit 3; +reset master; --exec $NDB_MGM --no-defaults -e "all restart -i" >> $NDB_TOOLS_OUTPUT --exec $NDB_TOOLS_DIR/ndb_waiter --no-defaults >> $NDB_TOOLS_OUTPUT @@ -60,6 +62,7 @@ select * from t2 order by a limit 3; --error ER_NO_SUCH_TABLE select * from t2; show tables like 't2'; +reset master; create table t2 (a int key) engine=ndbcluster; insert into t2 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10); select * from t2 order by a limit 3; @@ -67,6 +70,7 @@ select * from t2 order by a limit 3; # server 2 should have a stale cache, but with right frm, transaction need not be retried --connection server2 select * from t2 order by a limit 3; +reset master; drop table t2; # End of 4.1 tests |