Moving from 1 node to MySQL Cluster

[Venudhar Poluri]

Hello everyone,

We are exploring MySQL cluster installation. We want to install the My cluster on one node, and when we get to a scenario of more application load we want to go for the second node of MySQL cluster with a replication of data nodes.

However from the articles listed the MySQL cluster does not guarantee durable commits and that may be risky to run in one node.

so we are planning to start with InnoDB engine on the first node, and when we
go for a second node, we are converting that InnoDB engine to NLB cluster.

Can you suggest if there any other approach that we could follow? The main
concern we have is the customer will be adding node by node and we don't want
to ask more than one machine upfront.

Also we are exploring the following options to convert the engine as many forums explain, can you suggest which of them is better or any other better alternative?

1. create a dump using mysqldump, and drop/rename the original database, change the engine to NDBCLUSTER and restore it back.
2. Alter all the tables to drop the keys/indexes and alter the engine, and recreate keys.


Thanks for the help,
Venu