2 messages in com.mysql.lists.clusterExisting cluster - adding sql nodes /...
FromSent OnAttachments
James Wolner16 Feb 2006 04:24 
Stewart Smith20 Feb 2006 16:46 
Subject:Existing cluster - adding sql nodes / adding new datanodes / adding database schemas/tables
From:James Wolner (jam@wolner.se)
Date:02/16/2006 04:24:02 AM
List:com.mysql.lists.cluster

Good day!

I find it unclear as to what configuration steps need be taken after adding new nodes to an existing cluster.

This concerns SQL nodes and even datanodes.

SQL NODES

1. Configuring an added (new) SQL node to an existing Cluster.

1. Obviously, update the managment node's config.ini to include the SQL node in an [MYSQLD] section 2. Obviously, install the SQL node and put an ndbcluster and ndb-connectstring in the [MYSQLD] section of the SQL nodes my.cnf 3. Does an SQL node need the [mysql_cluster] section of the my.cnf file? http://dev.mysql.com/doc/refman/5.0/en/multi-config.html says that section is an option for the ndbd process. Should this be included in the my.cnf file of an SQL node or does an SQL node only use the [mysqld] section? 4. Obviously, start up the SQL node. 5. What about the schemas and tables. Do I have to import the data-structure (create empty tables and schemas) on each and every SQL node I add in the future. The reason I ask is because while testing adding a new SQL node that node did not see tables in the cluster, perhaps due to some other problem.

But, what steps should be taken and it what order?

1. I assume the managment node needs to be restarted to read the config.ini? Does the cluster continue to run while the management node re-reads the .ini file?

Simply, are there documented steps for adding new SQL nodes SQL nodes?

Same question for data nodes.

What is the recommended steps to include one or two new data nodes when a db cluster needs to be beefed-up.