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: | |
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 |
[20 May 2009 10:22]
Maciej Nadolski
[25 May 2009 13:17]
Jonathan Miller
Try creating table and then adding indexes doing on-line alter
[25 May 2009 13:49]
Maciej Nadolski
Did that. It works, but mysqldump can't be directly imported.
[25 May 2009 21:18]
Hartmut Holzgraefe
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.
[25 May 2009 21:25]
Hartmut Holzgraefe
Original cluster mailing list thread on this: http://lists.mysql.com/cluster/6642
[11 Aug 2009 12:55]
Jonas Oreland
duplicate of bug#45525
[11 Aug 2009 13:02]
Jonas Oreland
tested on (unrelease) 7.0.7 and it worked fine