MySQL Bugs: #44980: Too many schema operations while creating table

Bug #44980	Too many schema operations while creating table
Submitted:	20 May 2009 10:22	Modified:	11 Aug 2009 13:02
Reporter:	Maciej Nadolski	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	mysql-5.1-telco-7.0	OS:	Linux (CentOS 5.2)
Assigned to:	Jonas Oreland	CPU Architecture:	Any
Tags:	7.0.5

Description:
When trying to create or alter big table I get NDB error 783. I found in NDB developers API guide, that this is 'Too many schema operations'.

It can't be tuned, from guys on mysql-cluster list I found out it is a bug and has to be reported.

First I wasn't able to create table and I had to create it in steps, first creating simpler table and than altering it wis simple ALTERs. Now I see that even ALTER isn't possible.

'Can't create table 'dbname.#sql-3c49_a9a3' (errno: 783)' on query. Default database: 'dbname'. Query: 'ALTER TABLE tablename AUTO_INCREMENT = 20000000'

How to repeat:
Just try to create big table with > 120 attributes and >20 indices.

Suggested fix:
No idea

Try creating table and then adding indexes doing on-line alter

Did that.
It works, but mysqldump can't be directly imported.

Using CREATE TABLE i can only create tables with up to 15 indexes (16 including the primary key).

Using online CREATE INDEX or ALTER TABLE ADD INDEX it is possible to add more indexes which can be utilized just fine (both with and without condition pushdown.

A table created this way can't be dumped and restored using mysqldump though, and even worse: a DROP TABLE on such a table does never finish and puts a constant 30-40% CPU load on the data nodes until the hanging mysql client session is terminated.

Original cluster mailing list thread on this: http://lists.mysql.com/cluster/6642

duplicate of bug#45525

tested on (unrelease) 7.0.7 and it worked fine