Disk Data files and restarting data nodes using --initial

Hi,

I'd like to know what the recommended practice is for adding new nodes to the cluster on a disk-based system.

>From how I've understood things so far, any scale out we do on the
data node side will require that we back up our data as we would expect to lose all our data when starting up ndb on each node using --initial. And as from what I gather in a separate, currently-ongoing thread, --initial is required whenever a hardware change occurs.

A few moments ago, we did just that. We ran ndbd with the --initial flag on all data nodes and saw that disk data files are not removed when restarting a node using --initial. Fine, but then what is our recourse now since the two older nodes have these disk data files and the two new ones don't? Does the cluster recognize these data files, and if so, can it handle the fact that these files only exist in two of the storage nodes and not the other nodes?

-Al

-- 
MySQL Cluster Mailing List
For list archives: 
http://lists.mysql.com/cluster
To unsubscribe:    
http://lists.mysql.com/cluster?unsub=lists@pantek.com