Bug #34257 Creating tables on different mysql nodes causes inconsistencies
Submitted: 3 Feb 2008 0:40 Modified: 14 Feb 2008 5:04
Reporter: Jeff Wang Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.22 OS:Any
Assigned to: CPU Architecture:Any

[3 Feb 2008 0:40] Jeff Wang
Creating (different tables) using 2 mysql nodes will cause inconsistencies.  You will get an error saying the "table already exists" when trying to create, when it doesn't exist.  Ndb_show_tables will show the tables exist but trying to access it ( drop, select, desc) from a mysql shell does not work.  

Inconsistency issues persist even after system restart.  Note that I am using on disk data and did not test with normal table creations.

How to repeat:
Just issue (unique) create table statements using 2 different mysql nodes.
[3 Feb 2008 21:50] Adam Dixon
Are you able to describe steps to repeat your behavior?
Does mysql> show warnings; have any output when you receive an error? Can you provide this example.

# mysql -S /tmp/mysql.sock -u root test -e "create table t1(id int not null auto_increment, c1 char(24), primary key(id))engine=ndb;"

# mysql -S /tmp/mysql1.sock -u root test -e "create table t2(id int not null auto_increment, c1 char(24), primary key(id))engine=ndb;"

# mysql -S /tmp/mysql1.sock -u root test;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 6
Server version: 5.1.24-rc-debug-log Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show tables;
| Tables_in_test |
| t1             | 
| t2             | 
2 rows in set (0.01 sec)
[3 Feb 2008 21:54] Adam Dixon
Sorry, the same occurs when using disk table space in table create statements.
[4 Feb 2008 22:49] Jeff Wang
Odd, I cannot reproduce the inconsistencies anymore either. I can consistently get :

NDB error code 701: System busy with other schema operation: Temporary error: Overload error

But I don't get inconsistencies, so it's not that big of a deal.
[4 Feb 2008 22:54] Jeff Wang
script to reproduce 701 error

Attachment: CrashTest.java (, text), 2.68 KiB.

[14 Feb 2008 5:04] Valeriy Kravchuk
So, it looks like original problem is not repeatable.