Bug #15618 cluster alter table not sync on the other cluster node

• Submitted: 9 Dec 2005 8:32
• Modified: 9 Dec 2005 8:50
• Reporter: jeppeter wang
• Status: Not a Bug
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S2 (Serious)
• Version: 5.0.16
• OS: Linux (linux)
• CPU Architecture: Any

[9 Dec 2005 8:32] jeppeter wang

Description:
alter table information can not sync on the all nodes of a cluster

How to repeat:
i have find a bug in the cluster server.and it is when i create the table on one node ,i can see the creation on the othernode just like 
create table ctest (i BIGINT) ENGINE=NDBCLUSTER;

but when i alter the table columns in one node ,i can not find the sync information on the other node ,just like
alter table ctest add name VARCHAR(20) ;

but when i use 
describe ctest on the othernode ,i just see
field  type           null      key defaults extra
i       bigint(11)     yes          NULL      

not the name information .

[9 Dec 2005 8:50] Valeriy Kravchuk

Thank you for a problem report. Sorry, but it is not a bug. It is known and documented limitation of NDB Cluster. Please, read the manual (http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-limitations.html) for possible workaround:

"It is not possible to make online schema changes such as those accomplished using ALTER TABLE or CREATE INDEX, as the NDB Cluster does not support autodiscovery of such changes. (However, you can import or create a table that uses a different storage engine, then convert it to NDB using ALTER TABLE tbl_name  ENGINE=NDBCLUSTER;. In such a case, you need to issue a FLUSH TABLES command in order to force the cluster to pick up the change.)"