I've been spending a lot of time working to get a MySQL Cluster up and running. The docuementation leaves out a lot of critical info (or presents it in a less than optimal order). But I can mostly live with that.
However, one of the programs has confusing command line arguments. ndbd the "data node" piece of the NDB storage engine (which is all the cluster brains), cracks me up:
root@mysql1:/home/mysql/var/cluster# ../../libexec/ndbd -h Usage: ../../libexec/ndbd [--version] [-v] [--start] [-s] [--no-nostart] [-n] [--deamon] [-d] [--initial] [-i] [--connect-string=constr] [-c constr] [--usage] [-?] The MySQL Cluster kernel -v, --version Print version -s, --start Start ndb immediately -n, --no-nostart Don't start ndb immediately -d, --deamon Start ndb as deamon -i, --initial Start ndb immediately -c constr, --connect-string=constr "nodeid=
;host= " -?, --usage Print help
Okay, let me get this stright. There are two ways to make it start up immediately (-s and -i). But if you want it not to start immediately you'd use the poorly named --no-nostart option.
Which of those, if any, is the default if I specify none?
I've configured something wrong. My management node comes up fine but my first data node is decidedly unhappy. And the error it logs might as well be in ROT-13 octal.
Back to head scratching.
Once I get this working, I'll post my recipie and work to include it in the second edition of High Performance MySQL.
Update: I've got all four data nodes up and talking to the management node. Excellent. Now I need a client...
Posted by jzawodn at August 17, 2004 04:21 PM