MySuQL clustering that is. Looks like it’s pretty useless anyway tho as we’re trying to achieve high-availabilty… clustering only seems to give data-integrity and load-sharing… I beleive we want multi-master replication. Something to do tomorrw… this setup only took me about 2 days to get going.
Oh – and I’m not doing this for myself, this is for a client. I’m pushing PostgreSQL as much as I can 🙂

One really big problem I’m having is privileges are not propagating… I infer this is as result of the mysql schema and tables being stores as MyISAM tables, but when I altered them to use the ndbcluster engine, it just overwrote it’s peers in the cluster, but didn’t actually cluster the data.

[16:16:13] 0 root@dbc-ac:~$ ndb_mgm
— NDB Cluster — Management Client —
ndb_mgm> SHOW;
Connected to Management Server at: localhost:1186
Cluster Configuration
———————
[ndbd(NDB)] 2 node(s)
id=2 @172.17.4.140 (Version: 5.0.18, Nodegroup: 0, Master)
id=3 @172.17.4.141 (Version: 5.0.18, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @172.17.4.142 (Version: 5.0.18)

[mysqld(API)] 2 node(s)
id=4 @172.17.4.140 (Version: 5.0.18)
id=5 @172.17.4.141 (Version: 5.0.18)

ndb_mgm>^D
[16:16:31] 0 root@dbc-ac:~$